WO2018172542A1 - Manipulation de tampon de données pour double connectivité - Google Patents

Manipulation de tampon de données pour double connectivité Download PDF

Info

Publication number
WO2018172542A1
WO2018172542A1 PCT/EP2018/057519 EP2018057519W WO2018172542A1 WO 2018172542 A1 WO2018172542 A1 WO 2018172542A1 EP 2018057519 W EP2018057519 W EP 2018057519W WO 2018172542 A1 WO2018172542 A1 WO 2018172542A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
base station
radio base
preprocessing
grant
Prior art date
Application number
PCT/EP2018/057519
Other languages
English (en)
Inventor
Torsten DUDDA
Henning Wiemann
Jose Luis Pradas
Martin Skarve
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2018172542A1 publication Critical patent/WO2018172542A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/082—Load balancing or load distribution among bearers or channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling

Definitions

  • [001] Disclosed are embodiments related to sending uplink (UL) data for a split bearer using dual connectivity (DC).
  • UL uplink
  • DC dual connectivity
  • the 3 GPP is working on a New Radio (NR) standard for 5G, building on
  • the dual connectivity (DC) protocol architecture of a split bearer will be standardized, building on the protocol architecture used for LTE for the DC split bearer.
  • the UE maintains a packet data convergence protocol (PDCP) entity for the split bearer connected to multiple (e.g., two) radio link control (RLC) and medium access control (MAC) entities. These are each associated to a cell group, the master cell group and secondary cell group respectively. Transmission via the master cell group goes to the Master eNB (MeNB) (MgNB in NR or 5G terminology); transmission via the secondary cell group goes to the Secondary eNB (SeNB) (SgNB in NR or 5G terminology).
  • MeNB Master eNB
  • SeNB Secondary eNB
  • the MeNB and SeNB maintain their own RLC and MAC entities associated to this single split bearer.
  • a further node or function is involved, the packet processing function (PPF), which may be separate or collocated with the MeNB or SeNB, and the PPF terminates the PDCP protocol on the network side.
  • PPF packet processing function
  • the UE may transmit a PDCP protocol data unit (PDU) via either the MeNB or SeNB side.
  • PDU PDCP protocol data unit
  • two configuration parameters have been standardized: split threshold and prioritized cell group. If the data in the PDCP UL buffer (i.e., UL queue) is below the split threshold, transmission of the data is only allowed via the prioritized link/cell group/eNB; if the data in PDCP is higher than the threshold, transmission is allowed via both links/cell groups/eNBs.
  • the prioritized cell group can be configured to be either the MeNB or SeNB.
  • a problem with sending UL data for the split bearer in DC is that current approaches result in unnecessary latency.
  • the data Prior to transmitting data, the data must be processed into a PDCP PDU format. This processing is depending upon whether the MeNB or SeNB will be used for transmission. Current approaches therefore only begin processing after an UL grant has been received (and therefore after it is known whether the MeNB or SeNB will be used for transmission). This means that there is a delay between when the UE is authorized, via the UL grant, to transmit, and when that transmission takes place. This delay is at least as long as the processing time required to process the UL data into PDCP PDU format. Accordingly, improved approaches to sending UL data for split bearer in DC are needed.
  • NR wireless access networks and user equipments (UEs) implementing access technologies and standards other than NR (e.g., 3G, 4B).
  • NR e.g., 5G NR
  • 5G NR is used as an example technology for purposes of describing embodiments, but this disclosure is not so limited.
  • ultra-low latency for transmission, and processing is a fundamental requirement.
  • transmission of data in uplink in response to reception of an uplink grant should be done within a very short time (to be standardized).
  • This preprocessing may comprise assigning PDCP and RLC sequence numbers (SNs) to PDCP service data units (SDUs).
  • SNs RLC sequence numbers
  • SDUs PDCP service data units
  • embodiments provide that sending UL data for split bearer in DC can be efficiently operated with the use of the split threshold. For example, embodiments allow for immediate transmission of the UL data upon reception of an uplink grant. This is possible because of prescheduling or preprocessing of the UL data. Embodiments achieve this efficiency by using further pre-scheduling thresholds and other methods as described herein.
  • a method performed by a user equipment (UE) for managing or handling uplink (UL) data transmissions in a radio
  • UE user equipment
  • UL uplink
  • the method includes the UE preprocessing data prior to receiving a UL grant; and storing the preprocessed data in an UL data buffer.
  • preprocessing the UL data comprises preprocessing at least a first portion of the data specific to the first radio base station. In some embodiments, a size of the first portion is less than a difference between a first preprocessing high threshold and a first preprocessing low threshold.
  • preprocessing the first portion of the data specific to the first radio base station comprises re-processing at least a subpart previously preprocessed specific to the second radio base station.
  • preprocessing the data further comprises preprocessing at least a second portion of the data specific to the second radio base station.
  • a size of the second portion is less than a difference between a second preprocessing high threshold and a second preprocessing low threshold.
  • the first portion and the second portion overlap.
  • the method also includes: receiving a UL grant from the first or the second radio base station; and in response to receiving the UL grant, transmitting a portion of the preprocessed data to the corresponding first or second radio base station (e.g., as a result of receiving the UL grant, the device transmits the data immediately - e.g., the data is transmitted in a TTI for which the uplink grant is valid).
  • the UL grant is specific to the first radio base station, and the transmitted portion of data corresponds to a subset of the first portion. In some embodiments, the UL grant is specific to the second radio base station, and the transmitted portion of data corresponds to a subset of the second portion.
  • the method further includes receiving a first UL grant from the first radio base station; receiving a second UL grant from the second radio base station; in response to receiving the first UL grant, transmitting a portion of the data in the UL data buffer that corresponds to a subset of the first portion to the first radio base station (e.g., this data is transmitted in the TTI for which the first UL grant is valid); and in response to receiving the second UL grant, transmitting a portion of the data in the UL data buffer that corresponds to a subset of the second portion to the second radio base station (e.g., this data is transmitted in the TTI for which the second UL grant is valid).
  • the method further includes: determining that a current size of the UL data buffer is above or below a split threshold; in response to determining that the current size of the UL data buffer is below a split threshold, sending a scheduling request (SR) only to the first radio base station; in response to determining that the current size of the UL data buffer is above a split threshold, sending a SR to both of the first radio base station and the second radio base station.
  • SR scheduling request
  • the method further includes: receiving one or more of the first preprocessing high threshold, the first preprocessing low threshold, the second
  • preprocessing high threshold and the second preprocessing low threshold, from a node in the radio communications network.
  • the received thresholds are updated based on current network conditions.
  • the current network conditions comprise at least one of: the UE UL throughput to first radio base station and/or to second radio base station, the ratio of throughput between the first radio base station and the second radio base station, the TTI length for this UE, the link quality (SINR) to first radio base station and/or to second radio base station.
  • the UE receives the updated thresholds from the network and/or the UE performs the updating.
  • preprocessing the data in the UL data buffer comprises processing at least a portion of the data in the UL data buffer to create one or more packet data convergence protocol (PDCP) service data units (SDUs).
  • PDCP packet data convergence protocol
  • creating one or more PDCP SDUs comprises one or more of the following steps: assigning a PDCP sequence number (SN) to each of the PDCP SDUs; building a PDCP header for each of the PDCP SDUs; encrypting each of the PDCP SDUs to create one or more PDCP protocol data units (PDUs); assigning radio link control (RLC) SN to each of the PDCP PDUs; and building an RLC header for each of the PDCP PDUs.
  • the method includes placing the data in the UL data buffer prior to preprocessing the data.
  • a UE that has a preprocessing module configured to preprocess UL data prior to receiving a UL grant; and a storing module configured to store the preprocessed data in an UL data buffer.
  • the UE is further adapted to perform the method steps described above and herein.
  • FIG. 1 illustrates a split bearer network arrangement according to some embodiments.
  • FIG. 2 is a flow chart illustrating a process according to some embodiments.
  • FIG. 3. illustrates an UL data queue (buffer).
  • FIGs. 4A, 4B and 4C illustrate different scenarios according to some embodiment
  • FIG. 5A illustrates an arrangement according to some embodiments.
  • FIG. 5B illustrates an arrangement according to some embodiments.
  • FIG. 6 is a block diagram of a UE according to some embodiments.
  • FIG. 7 is a diagram showing functional modules of a UE according to some embodiments.
  • FIG. 1 illustrates a split bearer network arrangement according to some embodiments.
  • UE 102 is served by a first radio base station 103 (e.g., Master eNB or gNB, or MeNB) and a second radio base station 104 (e.g., Secondary eNB or gNB, or SeNB). Both MeNB 103 and SeNB 104 are coupled to a packet processing function (PPF) node 106.
  • PPF packet processing function
  • UE 102 further comprises a UL data buffer (i.e., a UL data queue). Generally, after data for uplink transmission is placed in the UL data buffer, UE 102 will transmit the data.
  • a UL data buffer i.e., a UL data queue
  • UE 102 is utilizing a dual connectivity (DC) split bearer, with a split threshold.
  • DC Transmission Time Interval
  • the UE 102 may only transmit the UL data to MeNB 104.
  • the UE 102 may use one or both of the MeNB 103 and SeNB 104 (e.g., some of the buffered data is transmitted to MeNB and another portion of the buffered data is transmitted to SeNB).
  • UE 102 preprocesses data in the UL data buffer.
  • the preprocessing is dependent on the link ultimately selected (i.e., on whether the MeNB or SeNB is used for data transmission).
  • the preprocessing may also be based on several threshold values, as presently described. For example, the split threshold as already been described above, may determines whether only MeNB or one or more of MeNB and SeNB will be used in uplink. Further preprocessing thresholds, such as the M-preProc-low threshold (first preprocessing low threshold, e.g.
  • the UL data buffer will be described as having a bottom or first position starting at 0 (lowest address of the buffer). For data at the position indicated by the M-preProc-low threshold (taken to be 0 throughout this discussion), and up to the position indicated by the M-preProc threshold, UE 102 preprocesses such data for transmission to the MeNB 103.
  • UE 102 For data at the position indicated by the S-preProc-low threshold (e.g. taken to be equal to the split threshold, unless otherwise noted), and up to the position indicated by the S- preProc threshold, UE 102 preprocesses such data for transmission to the SeNB 104.
  • the M-preProc threshold is greater than or equal to the S-preProc-low threshold (that may correspond to the split threshold), then there will be some overlap of data that UE 102 preprocesses for both MeNB 103 and SeNB 104.
  • the amount of overlap will be equal to the difference between the M-preProc threshold and the S-preProc-low threshold (e.g., split threshold).
  • the M-preProc threshold is less than the S-preProc-low threshold (e.g., split threshold)
  • An advantage to this preprocessing is that, when an UL grant is received, for example, an UL grant for MeNB 103 and another UL grant for SeNB 104, UE 102 is ready to send the preprocessed data. Therefore, it is advantageous for the difference between the M- preProc threshold and the M-preProc-low threshold to be greater than the maximum grant size on MeNB 103. Likewise, it is advantageous for the difference between the S-preProc threshold and the S-preProc-low threshold to be greater than the maximum grant size on SeNB 104. The reason for this is that otherwise it is possible that when a UL grant is received, not enough data will be ready (i.e. preprocessed) to fully utilize the UL grant resource. That is, either
  • FIG. 2 illustrates a process 200.
  • Process 200 may begin with step 202, where UE
  • Process 200 may further include step 204, preprocessing a first chunk of data specific for a first radio base station, the first chunk having a size less than or equal to a first preprocess threshold. For example, this may involve
  • Process 200 may further include step 206, preprocessing a second chunk of data specific for a second radio base station, the second chunk having a size less than or equal to a second preprocess threshold. For example, this may involve preprocessing data for SeNB 103, where the second chunk is equal to or less than the difference S-preProc and S-preProc-low (e.g., split threshold).
  • the UE 102 stores the preprocessed data in an UL data buffer.
  • step 210 the UE 102 performs a comparison to determine whether the current size of the UL data buffer is below a split threshold. If so, only transmission to the first radio base station is permitted, and so the UE 102 sends in step 212 a scheduling request (SR) only to the first radio base station. Otherwise, transmission over both the first and second radio base stations is permitted, and so the UE 102 sends in step 214 a SR to both first and second radio base stations.
  • SR scheduling request
  • FIG. 3 illustrates an arrangement 300 showing an uplink data buffer 302, e.g. an uplink PDCP buffer with a PDCP split buffer threshold 304.
  • the buffer 302 is filled up from the upper part (i.e. buffer position 0 is shown at the upper part, and the buffer position increases going downward).
  • Data in a position “below” the split threshold 304 i.e., data between buffer position 0 and the split threshold 304
  • M the prioritized link
  • S un-prioritized link
  • Data in a position “above” the split threshold e.g., data between the split threshold and the M-preProc threshold
  • the received uplink grant(s) determine where the data is sent.
  • Preprocessing data in the buffer includes, for example, taking steps to generate a
  • preprocessing data in the buffer may include one or more of: assigning a PDCP SN for the PDCP PDU, generating the PDCP header for the PDCP PDU, encrypting the data, placing the encrypted data in a payload portion of the PDCP PDU.
  • Preprocessing may further include assigning an RLC SN to the PDCP PDU, assigning the RLC header, and parts of the MAC header, e.g. length field.
  • the data routed over the MeNB (or master gNB) and the SeNB (or secondary gNB) will have independent RLC entities and, therefore, independent RLC SNs. That is, data must be processed specifically for either the MeNB (or master gNB) or the SeNB (or secondary gNB).
  • the UE should preprocess data ready for transmission over M up to a
  • preprocessing threshold 306 specific for M shown as M-preProc threshold 306
  • M-preProc threshold 306 This preprocessing threshold is assumed to be greater than or equal to the split threshold.
  • S-preProc threshold 308 shown as S-preProc threshold 308
  • the other preprocessing threshold can be chosen as an offset to the split threshold and should be larger than the maximum grant size on S.
  • the UE can be configured with the preprocessing thresholds for M and S, respectively. That is, for example, the network (e.g., base station or core network node) may be configured to send to the UE a message (e.g. a Radio Resource Control (RRC) message or a non-access stratum (NAS) message) that includes information indicating the preprocessing thresholds.
  • the network e.g., base station or core network node
  • RRC Radio Resource Control
  • NAS non-access stratum
  • the UE preprocesses data according to these configured preprocessing thresholds or to UE implementation specific thresholds (thresholds determined by the UE e.g. based on throughput).
  • the UE should at least preprocess all data below the split threshold, intended for the prioritized link direction.
  • the difference between S-preProc threshold and S-preProc-low threshold is zero (i.e., no preprocessing for S).
  • FIG. 3 there is an overlap area, where data is preprocessed twice: once for M and again for S. That is, data 310 that is preprocessed for M and data 312 that is preprocessed for S share some data in common.
  • This overlap depends on M-preProc threshold: if M-preProc threshold is less than S-preProc-low threshold (e.g., split threshold), there is no overlap; otherwise, the overlap size is the difference between M-preProc threshold and S- preProc-low threshold.
  • the UE in this case (where there is an overlap area), can keep duplicate data ready for potential transmission, where such duplicate data is differently preprocessed for M and S, respectively.
  • Embodiments are described below that describe the procedure for preprocessing in more detail. In particular, when preprocessing is done for a given link and how the UE acts upon receiving uplink grants.
  • FIGs. 4A, 4B and 4C illustrate three example scenarios 411, 412, and 413.
  • the UL data buffer 302 is filled with data exceeding the split threshold 304.
  • the UE may send a scheduling request (SR) to one or both of the M and S links.
  • SR scheduling request
  • uplink data arrives in the UL data buffer 302, and is not yet preprocessed (gray, squares), at transmission time interval (TTI) n-x.
  • TTI transmission time interval
  • buffer 302 includes some data that is ready for transmission on M, having been preprocessed already. That is, because the data is preprocessed it can be sent immediately, without the need for further processing into an appropriate format.
  • the M grant received indicates that the amount of UL data the UE can send as a result of receiving the M grant is less than the amount of data that has been preprocessed for M. Accordingly, as a result of receiving the M grant, the UE transmits the data that exists between buffer position 0 and the position indicated by reference number 415. This transmitted data is then removed from the buffer, and as shown in FIG.
  • the data that was preprocessed for M but not transmitted is repositioned in the buffer such that the data starts at buffer position 0 and ends at the position indicated by reference 416, and the data that was preprocessed for S but not transmitted is discarded.
  • an UL grant for M and an UL grant for S are received as in case 2.
  • the UL grant size for S is less than the size of data processed for S.
  • the remaining data at TTI n+1 is lower than the split threshold and thus can only be sent via M.
  • the preprocessed data above the data sent to S was already preprocessed for M and S, however needs reprocessing anyway, since the preprocessed data for M above the split threshold was preprocessed with the assumption that no S grant is received, and further the data preprocessed for S above the data sent on the grant for S needs preprocessing since it is part of the remaining data and can only be sent via M.
  • the re-preprocessing can be done until the TTI n+1. That is, the re-preprocessing can start at TTI n after the UL grants are received.
  • the re-preprocessing implies among other things that the RLC SN needs to be updated to account for the fact that the data is to be transmitted on the M link. Thus, the SN needs to be assigned accordingly. Depending on how much larger the split threshold is chosen compared to the M grant size, this data would remain anyway longer in the queue so that multiple TTIs could be spend for preprocessing.
  • FIG. 5A A further case is illustrated in FIG. 5A, where preprocessing of data is assumed to take 2 TTIs.
  • the split threshold and the M-preProc threshold are configured larger than a multiple of the maximum grant size, or as multiples of what can be transmitted within one TTI.
  • the thresholds should be set to more than 2 TTI (as shown in FIG. 5A, the thresholds are set to 3 times the maximum grant size).
  • the S-preProc threshold for which the offset should also be larger than multiple TTIs. This is advantageous so that preprocessed data is also available at a potential S-grant (not shown).
  • FIG. 5A the preprocessed data ready for transmission is shown with diagonal striped lines, while the data currently being preprocessed and thus not ready for transmission yet is shown as horizontal or vertical striped lines.
  • PDCP PDUs are OK to be received out of sequence in the receiver.
  • the out of sequence delivery would start the reordering timer, and the receiver waits to deliver subsequent PDUs until the outstanding PDUs are received (within reordering time).
  • the split threshold may be configurable dynamically, e.g. by
  • a PDCP control PDU may be used for this purpose.
  • the starting point for the S-preprocessing is the split threshold.
  • the S-preprocessing-threshold-low (S-preProc-low) is defined as the starting point, and may be configurable by the network, or determined by the UE, e.g. based on measurements or estimations of coming grants.
  • split threshold needs to be suddenly adapted to a lower value, e.g. due to very low throughput on M, e.g. at a coverage edge. In this situation only very low M grant sizes can be expected and it is useful to send data on S. Therefore, the split threshold is set to a very low value. To allow immediately after this adaptation, transmission on S, data needs already to be preprocessed. Therefore, the S-preProc-low value should already before the split-threshold reconfiguration be set to a very low value, as illustrated in FIG. 5B.
  • the UE applies the preprocessing and may set at least one of split threshold, S-preProc threshold and M-preProc threshold according to measured, averaged over time window, or expected throughput or UL allocation size, measured, averaged over time window, or expected radio quality, or according to capabilities, or according to current or expected UL queueing buffer sizes.
  • the UE may for the next TTI (e.g., of 1ms) preprocess at least an amount of data equal or above the certain throughput, so that this amount of data can be send immediately (in the TTI for which an uplink grant is valid) if the uplink grant is received for this link.
  • next TTI e.g., of 1ms
  • TTI e.g., of 1ms
  • FIG. 6 is a block diagram of UE 102 according to some embodiments.
  • UE 102 may comprise: a data processing apparatus (DP A) 602, which may include one or more processors (P) 655 (e.g., a general purpose microprocessor and/or one or more other processors, such as an application specific integrated circuit (ASIC), field-programmable gate arrays (FPGAs), and the like); a transmitter 605 and a receiver 604 coupled to an antenna 622 for enabling UE 102 to transmit data to and receive data from an AN node (e.g., base station); and local storage unit (a.k.a., "data storage system") 608, which may include one or more nonvolatile storage devices and/or one or more volatile storage devices (e.g., random access memory (RAM)).
  • a data processing apparatus DP A
  • P processors
  • ASIC application specific integrated circuit
  • FPGAs field-programmable gate arrays
  • FIG. 6 is a block diagram of UE 102 according to some
  • CPP 641 includes a computer readable medium (CRM) 642 storing a computer program (CP) 643 comprising computer readable instructions (CRI) 644.
  • CRM 642 may be a non-transitory computer readable medium, such as, but not limited, to magnetic media (e.g., a hard disk), optical media, memory devices (e.g., random access memory), and the like.
  • the CRI 644 of computer program 643 is configured such that when executed by data processing apparatus 602, the CRI causes UE 102 to perform steps described above (e.g., steps described above with reference to the flow charts).
  • UE 102 may be configured to perform steps described herein without the need for code. That is, for example, data processing apparatus 602 may consist merely of one or more ASICs. Hence, the features of the embodiments described herein may be implemented in hardware and/or software.
  • FIG. 7 is a diagram showing functional modules of UE 102 according to some embodiments.
  • UE 102 includes a preprocessing module 704 for preprocessing UL data prior to receiving a UL grant, a transmitting module 702 for employing a transmitter to transmit preprocessed data, a storing module 708 for storing data in a queue; and a receiving module 706 for employing a receiver to receive information (e.g., UL grants) transmitted by an AN node.
  • a preprocessing module 704 for preprocessing UL data prior to receiving a UL grant
  • a transmitting module 702 for employing a transmitter to transmit preprocessed data
  • a storing module 708 for storing data in a queue
  • a receiving module 706 for employing a receiver to receive information (e.g., UL grants) transmitted by an AN node.
  • information e.g., UL grants
  • LTE DC uplink split for the split bearer was introduced in Rel-13.
  • the UE is enabled to split its uplink PDCP queue among the two logical channels (RLCs) associated with the different cell groups (MAC entities) of MeNB and SeNB, and thus increase its uplink data rate.
  • the UE performs "routing" of PDCP PDUs to the respective cell groups.
  • the UE when indicating the data available for transmission to a MAC entity for BSR triggering and Buffer Size calculation, the UE shall:
  • the transmitting PDCP entity shall:
  • Buffered data below the split threshold is only indicated as available for transmission for BSR reporting to the prioritized cell group, while when buffered data is above the split threshold, data is indicated to both cell groups.
  • a transmission to lower layers is only done upon request from lower layers, i.e. at uplink grant reception. Otherwise the data remains on PDCP layer.
  • the buffered data is below the threshold, data is only submitted to the prioritized cell group; if buffered data is above the threshold, data can be submitted to either MCG or SCG cell group, i.e. to the requesting cell group.
  • the uplink split is configurable threshold based.
  • the solution for LTE may be used as a baseline.
  • LTE uplink split and PDCP design
  • the solution for LTE may be used as a baseline.
  • NR one may consider the following further requirements as compared to LTE, for UL split design:
  • NR link rates may be significantly different on MCG and SCG and may vary stronger. This applies both to NR-NR DC and NR-LTE DC, where MCG and SCG may correspond to links with different number of carriers, different carrier frequencies, different numerologies and TTI lengths. The UL split design should efficiently consider these varying throughputs on the links.
  • Low latency in NR a general design target is low latency, i.e. minimizing the processing and transmission time over L2, especially the best case latency when no queuing effects are present.
  • Latency and processing difference among links depending on numerology on NR link, or in case of LTE and NR integration, on difference in general latency and processing time, as well as backhaul connection, it is preferable to prioritize the faster link in case of no buffering instead of splitting data unnecessarily.
  • UL split design in NR may consider: link rate differences, latency and processing time differences, as well as the generally significantly shorter latency and processing time in NR, i.e. between grant reception and transmission.
  • the split threshold base solution can fulfil above-mentioned requirements for
  • Data below the split threshold is sent via a configurable prioritized link, which can be chosen to the be fastest link. This way, low latency and jitter is ensured.
  • Data below the split threshold may only be sent via the prioritized cell group.
  • all PDCP data below the split threshold can be preprocessed readily before an uplink grant is received with the correct assumption that later transmission is done on the prioritized cell group.
  • I.e. PDCP SN is assigned, encryption is done, as well as RLC SN of RLC associated with the prioritized cell group is done.
  • the uplink grant arrives, the data can be in-sequence transmitted via low layers.
  • PDCP would need to apply reordering only due to HARQ and RLC out of sequence deliveries within this cell group. This would lead to some jitter same as in single connectivity.
  • Data above the split threshold may be sent via one of both cell groups, depending on which cell group the uplink grant is available first. This way, all received grants can be utilized.
  • data may be transmitted and eventually received out of order at the PDCP receiver.
  • the PDCP receiver applies reordering so that this out of order delivery will eventually be visible as jitter to higher layers, where the jitter relates to the skew time between the transmitted blocks among both the links.
  • Preprocessing of data above the split threshold is also possible, so that it ready for transmission when a grant is available on MCG or SCG.
  • Data above the split threshold can also be sent via the prioritized link, in case the split threshold is smaller than the maximum grant size on the prioritized link. This can be avoided by configuring higher split thresholds.
  • the UE could preprocess chunks of data according to expected grant sizes in subsequent TTIs.
  • the UE also gives responsibility of this data to lower layers before the grant are received, the data needs to be transmitted also eventually via the lower layer the preprocessing was done for. This is not a problem if the grant is eventually received within the PDCP reordering time. This way, a potential delay because the grant was not received when/as large as expected, is eventually only visible as jitter to higher layers.
  • the UE keeps all data on PDCP (e.g. assigns RLC SNs, but by this does not affect RLC transmitter state) and does only give responsibility of the data to lower layers once the grant is received, the before mentioned jitter can be mostly avoided.
  • a re-preprocessing may to be done (e.g. discarding previous tentative SN assignments and assigning new SNs), so that at a next TTI preprocessed data is again available for the potentially received uplink grants.
  • the split threshold is configured based on RRC
  • split threshold configurable by PDCP control signaling (which by the network could be sent via the link with the highest throughput to the UE).
  • the uplink link direction should be quickly adaptable to the link with highest throughput, e.g. in case the other link suffers from throughput degradation, e.g. due to fading.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé mis en œuvre par un équipement utilisateur, UE (102), pour gérer ou manipuler des transmissions de données de liaison montante, UL, dans un réseau de communication radio, l'UE étant desservi par une première station de base radio (103) et une seconde station de base radio (104) fournissant une connectivité double à l'UE dans le réseau de radiocommunication, le procédé consistant à prétraiter des données UL avant de recevoir un octroi UL, et à stocker les données prétraitées dans un tampon de données UL (302). L'invention concerne en outre un UE (102) correspondant.
PCT/EP2018/057519 2017-03-24 2018-03-23 Manipulation de tampon de données pour double connectivité WO2018172542A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762476314P 2017-03-24 2017-03-24
US62/476314 2017-03-24

Publications (1)

Publication Number Publication Date
WO2018172542A1 true WO2018172542A1 (fr) 2018-09-27

Family

ID=61837746

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2018/057519 WO2018172542A1 (fr) 2017-03-24 2018-03-23 Manipulation de tampon de données pour double connectivité

Country Status (1)

Country Link
WO (1) WO2018172542A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109618419A (zh) * 2018-12-19 2019-04-12 中兴通讯股份有限公司 一种用于支持双连接的安全处理方法及系统
CN111510953A (zh) * 2020-04-26 2020-08-07 Oppo广东移动通信有限公司 一种数据处理方法及终端、存储介质
WO2020209629A1 (fr) * 2019-04-12 2020-10-15 Samsung Electronics Co., Ltd. Dispositif électronique prenant en charge une double connectivité et son procédé de fonctionnement
EP3768038A1 (fr) * 2019-07-17 2021-01-20 Samsung Electronics Co., Ltd. Dispositif électronique pour la transmission de données par l'intermédiaire d'une porteuse divisée et procédé de fonctionnement du dispositif électronique
WO2021010587A1 (fr) * 2019-07-17 2021-01-21 Samsung Electronics Co., Ltd. Dispositif électronique servant à transmettre des données par l'intermédiaire d'une porteuse divisée et procédé de fonctionnement de dispositif électronique
WO2022039918A1 (fr) * 2020-08-19 2022-02-24 Qualcomm Incorporated Surveillance de trafic de protocole de convergence de données par paquets (pdcp) pour la division dynamique de données

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017003118A1 (fr) * 2015-07-01 2017-01-05 Lg Electronics Inc. Procédé de transmission de données dans une connectivité double et dispositif pour cela
EP3122114A1 (fr) * 2014-03-18 2017-01-25 NTT DoCoMo, Inc. Équipement d'utilisateur et procédé de transmission de données de liaison montante

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3122114A1 (fr) * 2014-03-18 2017-01-25 NTT DoCoMo, Inc. Équipement d'utilisateur et procédé de transmission de données de liaison montante
WO2017003118A1 (fr) * 2015-07-01 2017-01-05 Lg Electronics Inc. Procédé de transmission de données dans une connectivité double et dispositif pour cela

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Pre-processing for NR-NR DC", vol. RAN WG2, no. Athens, Greece; 20170213 - 20170217, 12 February 2017 (2017-02-12), XP051212442, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170212] *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109618419A (zh) * 2018-12-19 2019-04-12 中兴通讯股份有限公司 一种用于支持双连接的安全处理方法及系统
WO2020209629A1 (fr) * 2019-04-12 2020-10-15 Samsung Electronics Co., Ltd. Dispositif électronique prenant en charge une double connectivité et son procédé de fonctionnement
CN111818668A (zh) * 2019-04-12 2020-10-23 三星电子株式会社 支持双连接的电子装置及操作该电子装置的方法
US11678221B2 (en) 2019-04-12 2023-06-13 Samsung Electronics Co., Ltd. Electronic device supporting dual connectivity and method of operating the same
EP3768038A1 (fr) * 2019-07-17 2021-01-20 Samsung Electronics Co., Ltd. Dispositif électronique pour la transmission de données par l'intermédiaire d'une porteuse divisée et procédé de fonctionnement du dispositif électronique
WO2021010587A1 (fr) * 2019-07-17 2021-01-21 Samsung Electronics Co., Ltd. Dispositif électronique servant à transmettre des données par l'intermédiaire d'une porteuse divisée et procédé de fonctionnement de dispositif électronique
US11337104B2 (en) 2019-07-17 2022-05-17 Samsung Electronics Co., Ltd. Electronic device for transmitting data through split bearer and method of operating electronic device
CN111510953A (zh) * 2020-04-26 2020-08-07 Oppo广东移动通信有限公司 一种数据处理方法及终端、存储介质
CN111510953B (zh) * 2020-04-26 2023-10-03 Oppo广东移动通信有限公司 一种数据处理方法及终端、存储介质
WO2022039918A1 (fr) * 2020-08-19 2022-02-24 Qualcomm Incorporated Surveillance de trafic de protocole de convergence de données par paquets (pdcp) pour la division dynamique de données
US11304198B2 (en) 2020-08-19 2022-04-12 Qualcomm Incorporated Packet data convergence protocol traffic monitoring

Similar Documents

Publication Publication Date Title
US11019519B2 (en) Method for calculating an amount of data available for transmission and a device therefor
US10708940B2 (en) Method and apparatus for reporting buffer state by user equipment in communication system
US11202279B2 (en) Method and apparatus for processing data in wireless communication system
US11432223B2 (en) Methods and apparatuses for selecting a first base station or a second base station to transmit a packet data unit (PDU) to a user equipment (UE)
KR101998016B1 (ko) 데이터의 전송을 제어하기 위한 방법
WO2018172542A1 (fr) Manipulation de tampon de données pour double connectivité
EP3509345B1 (fr) Procédé de déclenchement et d&#39;élaboration de rapports d&#39;état d&#39;un tampon et dispositif correspondant
KR101454524B1 (ko) 중계기에서의 서비스 품질 제어
JP7396768B2 (ja) グラントフリー伝送のためのアップリンクデータスケジューリングのためのシステムおよび方法
WO2015141478A1 (fr) Dispositif utilisateur et procédé de transmission de données de liaison montante
US20160149686A1 (en) Base station, user equipment for integrating multiple rats using carrier aggregation and methods thereof
WO2015016574A1 (fr) Procédé de calcul et de signalement d&#39;un état de tampon et dispositif à cet effet
EP3226606B1 (fr) Procédé pour l&#39;agrégation ran-wlan
JP2023015208A (ja) 送信装置、基地局及び無線通信システム
WO2018031020A1 (fr) Gestion d&#39;unité de données de protocole (pdu) d&#39;un protocole de convergence de données par paquets (pdcp) pour la mobilité entre une nouvelle technologie d&#39;accès radio et une évolution à long terme
WO2014126062A1 (fr) Système de communication mobile
JP2019068459A (ja) 基地局

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18714742

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18714742

Country of ref document: EP

Kind code of ref document: A1