EP3874647A1 - Mappage de lch vec un id processus harq pour des réseaux non terrestres - Google Patents

Mappage de lch vec un id processus harq pour des réseaux non terrestres

Info

Publication number
EP3874647A1
EP3874647A1 EP19839128.6A EP19839128A EP3874647A1 EP 3874647 A1 EP3874647 A1 EP 3874647A1 EP 19839128 A EP19839128 A EP 19839128A EP 3874647 A1 EP3874647 A1 EP 3874647A1
Authority
EP
European Patent Office
Prior art keywords
indication
base station
harq process
bundling
harq
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP19839128.6A
Other languages
German (de)
English (en)
Inventor
Helka-Liina Määttanen
Björn Hofström
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3874647A1 publication Critical patent/EP3874647A1/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements

Definitions

  • the present disclosure relates to communications networks and, more specifically, to Hybrid Acknowledgement Repeat Request (HARQ) for HARQ.
  • HARQ Hybrid Acknowledgement Repeat Request
  • Satellite networks could complement mobile networks on the ground by providing connectivity to underserved areas and multicast/broadcast services.
  • LTE Long Term Evolution
  • NR New Radio
  • 3GPP Third Generation Partnership Project
  • 3GPP Third Generation Partnership Project
  • This initial study focused on the channel model for the non-terrestrial networks, defining deployment scenarios, and identifying the key potential impacts.
  • 3GPP is conducting a follow-up study item in Release 16 on solutions evaluation for NR to support non-terrestrial networks (see RP-181370, Study on solutions evaluation for NR to support non-terrestrial Network, incorporated by reference).
  • a satellite radio access network usually includes the following components:
  • Feeder link that refers to the link between a gateway and a satellite
  • Service link that refers to the link between a satellite and a terminal
  • the link from gateway to terminal is often called forward link, and the link from terminal to gateway is often called return link.
  • forward link the link from terminal to gateway is often called forward link.
  • return link the link from terminal to gateway.
  • Bent pipe transponder satellite forwards the received signal back to the earth with only amplification and a shift from uplink frequency to downlink frequency.
  • Regenerative transponder satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth.
  • a satellite may be categorized as Low Earth Orbiting (LEO), Medium Earth Orbiting (MEO), or Geostationary (GEO) satellite.
  • LEO Low Earth Orbit
  • MEO Medium Earth Orbit
  • GEO Geostationary
  • LEO typical heights ranging from 500 - 1 ,500 km, with orbital periods ranging from 10 - 40 minutes.
  • MEO typical heights ranging from 5,000 - 12,000 km, with orbital periods ranging from 2 - 8 hours.
  • GEO typical height is about 35,786 km, with an orbital period of 24 hours.
  • a communication satellite typically generates several beams over a given area.
  • the footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell.
  • the footprint of a beam is also often referred to as a spotbeam.
  • the footprint of a beam may move over the earth surface with the satellite movement or may be earth fixed with some beam pointing mechanism used by the satellite to compensate for its motion.
  • the size of a spotbeam depends on the system design, which may range from tens of kilometers to a few thousands of kilometers.
  • Figure 1 shows an example architecture of a satellite network with bent pipe transponders.
  • the two main physical phenomena that affect satellite communications system design are the long propagation delay and Doppler effects.
  • the Doppler effects are especially pronounced for LEO satellites.
  • Propagation delay is a main physical phenomenon in a satellite communication system that makes the design different from that of a terrestrial mobile system.
  • the following delays are relevant.
  • the propagation delay depends on the length of the signal path, which further depends on the elevation angles of the satellite seen by the BS and UE on the ground.
  • the minimum elevation angle is typically more than 10° for UE and more than 5° for BS on the ground.
  • Table 1 Propagation delays for GEO satellite at 35,786 km (extracted from Table 5.3.2.1 -1 in 3GPP TR 38.81 1 V15.0.0, Study on New Radio (NR) to support non-terrestrial networks, incorporated by reference
  • the delay can be divided into a common delay component and a differential delay component.
  • the common delay is the same for all UEs in the cell and is determined with respect to a reference point in the spot beam.
  • the differential delay is different for different UEs which depends on the propagation delay between the reference point and the point at which a given UE is positioned within the spot beam.
  • the differential delay is mainly due to the different path lengths of the service links, since the feeder link is normally the same for terminals in the same spotbeam. Further, the differential delay is mainly determined by the size of the spotbeam. It may range from sub-millisecond (for spotbeam on the order of tens of kilometres) to tens of millisecond (for spotbeam on the order of thousands of kilometres).
  • the objectives of the current SI are to evaluate solutions for the identified key impacts from the preceding SI and to study impact on Radio Access Network (RAN) protocols/architecture.
  • the objectives for layer 2 and above are:
  • Propagation delay Identify timing requirements and solutions on layer 2 aspects, MAC, RLC, RRC, to support non terrestrial network propagation delays considering FDD and TDD duplexing mode. This includes radio link management. [RAN2]
  • Non Geo stationary satellites that move at much higher speed but over predictable paths [RAN2, RAN1 ]
  • NTN Non-Terrestrial Network
  • Satellite or aerial vehicles typically generate several beams over a given area.
  • the foot print of the beams are typically elliptic shape.
  • the beam footprint may be moving over the earth with the satellite or the aerial vehicle motion on its orbit.
  • the beam foot print may be earth fixed, in such case some beam pointing mechanisms (mechanical or electronic steering feature) will compensate for the satellite or the aerial vehicle motion.
  • TR 38.821 V0.1 .0 describes scenarios for the NTN work as follows:
  • Non-Terrestrial Network typically features the following elements:
  • a GEO satellite is fed by one or several sat-gateways which are deployed across the satellite targeted coverage (e.g. regional or even continental coverage).
  • sat-gateways which are deployed across the satellite targeted coverage (e.g. regional or even continental coverage).
  • UE in a cell are served by only one sat- g ate way -
  • a Non-GEO satellite served successively by one sat-gateway at a time.
  • the system ensures service and feeder link continuity between the successive serving sat-gateways with sufficient time duration to proceed with mobility anchoring and hand-over
  • Table 4.2-1 Reference scenarios
  • Table 4.2-2 Reference scenario parameters NOTE 1 : Each satellite has the capability to steer beams towards fixed points on earth using beamforming techniques. This is applicable for a period of time corresponding to the visibility time of the satellite
  • scenario D which is LEO with regenerative payload
  • scenario D both earth- fixed and earth moving beams have been listed. So, when we factor in the fixed/non-fixed beams, we have an additional scenario.
  • the complete list of 5 scenarios in 38.821 is then:
  • Embodiments described herein provide mapping of data to specific HARQ process IDs.
  • Certain embodiments of the present disclosure introduce systems, methods and apparatuses to map specific data to specific HARQ processes to allow some data to be sent with the HARQ procedure enabled and for other data, disabled.
  • a method includes at least one of receiving an indication that maps data that can be sent on one or more of specific HARQ processes, and transmitting/receiving (WT406) a transmission for the specific HARQ process based on the received indication.
  • the indication comprises a parameter for logical channel prioritization, LCP.
  • the indication is a grant or within a grant.
  • the method further includes including only data from specific logical channels, LCH, that are allowed to send data on HARQ processes with HARQ feedback disabled, based on the received indication.
  • the wireless device interprets that any logical channel, LCH, is valid for a grant.
  • the method further includes receiving
  • WT104 from the base station, an indication of a number of repetitions to use for bundling for the specific HARQ process.
  • a method performed by a base station for mapping data to specific HARQ processes includes at least one ohdetermining (e.g., deciding) an indication for mapping data and sending to a user equipment an indication that maps data that can be sent on one or more of specific HARQ processes.
  • the indication comprises a parameter for logical channel prioritization, LCP.
  • the indication is a grant or within a grant.
  • the method further includes including only data from specific logical channels, LCH, that are allowed to send data on HARQ processes with HARQ feedback disabled, based on the received indication.
  • the wireless device interprets that any logical channel, LCH, is valid for a grant. .
  • the method further includes receiving, from the base station, an indication of a number of repetitions to use for bundling for the specific FIARQ process.
  • wireless devices and base stations for deactivating FIARQ mechanisms including processing circuitry configured to perform any of the steps of any of the methods according to the embodiments, are provided.
  • Figure 1 shows an example architecture of a satellite network with bent pipe transponders
  • Figure 2 illustrates typical beam patterns of various NTN access networks
  • FIG. 3 illustrates various delays associated with the Hybrid
  • FIARQ Automatic Repeat Request
  • Figure 4 illustrates the operation of a base station and a User
  • UE Equipment
  • Embodiment 1 the embodiment denoted herein as“Embodiment 1” ;
  • Figure 5 illustrates the operation of a base station and a UE in accordance with at least some aspects of some embodiments of the present disclosure (e.g. the embodiment denoted herein as“Embodiment 2”);
  • Figure 6 illustrates the operation of a base station and a UE in accordance with at least some aspects of some embodiments of the present disclosure (e.g. the embodiment denoted herein as“Embodiment 3”);
  • Figure 7 illustrates the operation of a base station 302 and a UE 308 in accordance with at least some aspects of some embodiments of the present disclosure (e.g. the embodiment denoted herein as“Embodiment 6”);
  • Figure 8 through 10 illustrate example embodiments of a radio access node
  • Figure 1 1 and 12 illustrate example embodiments of a UE
  • Figure 13 illustrates a communication system including a
  • telecommunication network which comprises an access network and a core network, in which embodiments of the present disclosure may be implemented;
  • Figure 14 illustrates example implementations, in accordance with an embodiment, of the UE, base station, and host computer of Figure 13;
  • Figures 15 through 18 are flowcharts illustrating methods implemented in a communication system, in accordance with various embodiments.
  • Radio Node As used herein, a“radio node” is either a radio access node or a wireless device.
  • Radio Access Node As used herein, a“radio access node” or“radio network node” is any node in a radio access network of a cellular
  • a radio access node includes, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high- power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.
  • a base station e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network
  • a high- power or macro base station e.g., a micro base station, a pico base station, a home eNB, or the like
  • a“core network node” is any type of node in a core network.
  • Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P- GW), a Service Capability Exposure Function (SCEF), or the like.
  • MME Mobility Management Entity
  • P- GW Packet Data Network Gateway
  • SCEF Service Capability Exposure Function
  • a“wireless device” is any type of device that has access to (i.e. , is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s).
  • Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device.
  • UE User Equipment device
  • MTC Machine Type Communication
  • Network Node As used herein, a“network node” is any node that is either part of the radio access network or the core network of a cellular communications network/system.
  • Hybrid Automatic Repeat Request (FIARQ) protocol refers to the FIARQ procedure at the Physical (PHY) / Medium Access Control (MAC) layer.
  • PHY Physical
  • MAC Medium Access Control
  • the gNB may initiate up to 16 (8) new data transmissions without waiting for an ACK for the first packet transmission. Note that there are sufficient number of HARQ processes for terrestrial networks where the propagation delay is typically less than 1 ms.
  • Figure 3 shows the various delays associated with the HARQ procedure:
  • the receiver sends the feedback after a processing/slot delay T1 .
  • the transmitter may send a retransmission or new data after a processing/slot delay T2.
  • the existing HARQ mechanism may not be feasible when the propagation delay is much larger than that supported by the allowed number of HARQ processes.
  • the RTT propagation delay can be around 500ms.
  • the eNB needs to wait for around 500ms before sending new data. This translates to benefitting from only a meager fraction (8/500) of the available peak throughput. Therefore, without a sufficient number of HARQ processes, the sheer magnitude of the propagation delay may render closed-loop HARQ communication impractical.
  • the number of HARQ processes supported by the existing HARQ protocol are not sufficient to absorb the potentially large propagation delays in non-terrestrial networks.
  • Table 3 shows that a substantial increase in the existing number of HARQ processes (Note: Rel-15 NR supports a maximum of 16 HARQ processes in UL/DL per serving cell. LTE supports 8 for UL/DL per serving cell) is required for operating HARQ amid large propagation delays.
  • Rel-15 NR supports a maximum of 16 HARQ processes in UL/DL per serving cell.
  • LTE supports 8 for UL/DL per serving cell
  • a large number of HARQ buffers implies a large number of HARQ receivers.
  • activating the HARQ feedback loop may considerably reduce the throughput due to the inherent stop-and-wait property of the HARQ protocol.
  • the eNB/gNB/UE need not wait for the HARQ feedback or retransmissions before transmitting new data.
  • it helps saves the time/frequency/energy/computational resources required for HARQ feedback transmission.
  • the HARQ procedure is turned off or altered, there is a risk that the reliability is reduced due to the non-exiting feedback.
  • the reliability could then be increased by using more robust modulation and coding schemes but only to a certain extent. If transport blocks with errors are passed up to higher layers, e.g. RLC, PDCP, TCP, retransmission may occur which will again increase the delay mitigating some of the effect of disabling the HARQ procedure.
  • the network In current NR and LTE specifications, the network is in control of what LCHs that shall be served in DL for a given TB. I.e. it is up the network implementation to concatenate data so that bitrates for the different LCH are fulfilled. A TB will then be sent using the next in order and available HARQ process ID.
  • Logical Channel Prioritization procedure configured by RRC, that controls the amount of data that will be sent from each of the available LCH until the size of the TB meet the allocated size indicated in the grant. The TB will then be sent using the next in order and available HARQ process ID.
  • Embodiments described herein provide mapping of data to specific HARQ process IDs.
  • Embodiments of the proposed solution introduce methods for to map specific data to specific HARQ processes to allow some data to be sent with the HARQ procedure enabled and for other data, disabled. .
  • the satellite-based radio access network 300 is a radio access network for a cellular communications network such as, e.g., a LTE or NR network.
  • the satellite-based radio access network 300 includes, in this example, a base station 302 that connects the satellite-based radio access network 300 to core network (not shown).
  • the base station 302 is connected to a ground-based base station antenna 304 that is, in this example, remote from (i.e., not collocated with) the base station 302.
  • the satellite-based radio access network 300 also includes a satellite 306, which is a space-borne platform, that provides a satellite-based access link to a User Equipment (UE)
  • UE User Equipment
  • feeder link refers to the link between the base station 302 (i.e. , the base station antenna 304 in this example in which the base station 302 and the base station antenna 304 are not collocated) and the satellite 306.
  • service link refers to the link between the satellite 306 and the UE 308.
  • the link from the base station 302 to the UE 308 is often called the“forward link”, and the link from UE 308 to base station 302 is often called the“return link” or “access link.”
  • the“forward link” the link from the base station 302 to the UE 308
  • the“return link” or “access link” the link from UE 308 to base station 302
  • two transponder options can be considered:
  • Bent pipe transponder satellite forwards the received signal back to the earth with only amplification and a shift from uplink frequency to downlink frequency.
  • Regenerative transponder satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the earth.
  • an aggregation factor is a number that represents the number of times that the transport block will be retransmitted within a bundle. Without the capability of controlling aggregation factors for different HARQ processes, a single aggregation factor has to be used for all the HARQ processes regardless whether the HARQ feedback is
  • aggregation factor 1
  • Transport Block transmission errors associated with HARQ process(es) without HARQ feedback
  • RLC AM mode a proportion of Transport Block transmission errors (associated with HARQ process(es) without HARQ feedback) than what is designed in the specification needs to be recovered by higher layer retransmission techniques, such as RLC AM mode, PDCP, RRC or TCP. This results in a much higher latency and a reduced throughput. To avoid this, a large value needs to be configured for the
  • Embodiments 6 in particular, is aiming at addressing some of the challenges identified above, with respect to mapping data to HARQ processes. While described separately, these embodiments may be used in any desired combination.
  • bundling of transport blocks (TBs) is enabled for a specific HARQ process (e.g., a HARQ process identified by a specific HARQ process ID). This is sometimes referred to herein as“HARQ process specific bundling”.
  • Bundling is available in NR for both uplink and downlink and for both dynamic and configured scheduling. In the existing NR specification, however, bundling can only be activated for all transmissions on all configured HARQ processes. That is, bundling cannot be activated for a specified subset of HARQ processes. Given the proposed ability to disable the HARQ feedback for one or more specific HARQ processes (see U.S. Provisional Patent Application Serial No.
  • the reliability would decrease for all TBs sent using these HARQ processes if the aggregation factor is small or not configured. Since not all HARQ processes will have their feedback disabled, it will be useful to increase the reliability by allowing bundling for one or more specific HARQ process IDs (e.g., using HARQ process specific aggregation factor).
  • Example: HARQ Process ID 2 has its HARQ feedback disabled but is at the same time configured for bundling.
  • this HARQ process is used for transmission of a TB, it is bundled and the receiver knows how to receive and process these TBs within the bundle.
  • the reception and processing of TBs within the bundle can be performed in any suitable manner such as, e.g., the conventional manner.
  • the transmitter desires not using bundling, it may use a HARQ process ID not configured for bundling.
  • HARQ process specific bundling could be used for HARQ process having a specific HARQ process ID regardless of whether HARQ feedback is disabled or not for that HARQ process.
  • Which HARQ process to bundle in uplink or downlink can be indicated in any suitable manner such as e.g. indicated dynamically in the received DCI using a bit indication, indicated using a specific RNTI(s), indicated using a MAC CE, indicated semi-static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the aggregation factor to be used for bundling (e.g., for HARQ-disabled transmission) is configured, e.g., semi-statically (e.g., via RRC signaling). Further, in some embodiments, bundling is enabled for all transmissions using a HARQ process(es) for which HARQ mechanism(s) are disabled. Some examples of how HARQ mechanisms can be disabled are described in see U.S. Provisional Patent Application Serial No. 62/737,630 filed September 27, 2018, incorporated by reference.
  • the New Data Indicator (NDI) field in the DCI scheduling a transmission for a specific HARQ process is used to indicate whether bundling is enabled for the HARQ process or not.
  • NDI New Data Indicator
  • the NDI fields for those HARQ processes may be redundant.
  • the NDI fields for those HARQ processes can be repurposed, for example using new signaling (e.g.,
  • RRC signaling to indicate whether or not bundling is activated for the respective HARQ processes.
  • Figure 4 illustrates the operation of a base station 302 and a UE 308 in accordance with at least some aspects of Embodiment 1 described above. Optional steps are represented with dashed lines.
  • the base station 302 optionally determines (e.g., decides) to enable bundling for a specific HARQ process(es) (step 400). For example, the base station 302 may determine to enable bundling for a HARQ process(es) for which HARQ mechanism(s) have been disabled.
  • the HARQ process(es) for which bundling is enabled is a subset of all configured HARQ processes.
  • the base station 402 provides an indication to the UE 302 of the HARQ process(es) for which bundling is enabled (step 402).
  • This indication can be provided to the UE 308 in any suitable manner such as e.g. indicated dynamically in the received DCI using a bit indication, indicated using a specific RNTI(s), indicated using a MAC CE, indicated semi static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the base station 302 also provides, to the UE 308, an indication of the number of bundles to use (step 404).
  • the UE 308 receives the indication in step 402 and optionally the indication in step 404 and, based on the received indication(s), determines that bundling is enabled for the specific indicated HARQ process(es) (step 406).
  • the UE 308 and the base station 312 then perform DL/UL data transmission/reception associated with the indicated HAR process(es) with bundling enabled (step 408).
  • bundling of non-contiguous received/transmitted TBs is enabled for a specific HARQ process(es) . If configured, this would allow the network or UE to send TBs with the same HARQ process ID not necessarily contiguously, i.e., non-contiguous bundling. This would allow the transmitter to spread transmissions to achieve time diversity and avoid temporary radio propagation obstacles such as fast fading and, if delay tolerable, even slow fading mechanisms.
  • the current NR specification states that if the UE is configured with aggregationF actor > 1 (i.e., bundling is enabled), the same symbol allocation is applied across the aggregationF actor consecutive slots, and the UE may expect that the TB is repeated within each symbol allocation among each of the aggregationF actor consecutive slots.
  • a non-contiguous bundling pattern (i.e. , a pattern that defines the location of the bundled TBs, e.g., in time (and optionally frequency)) can be indicated to the UE in any suitable manner such as e.g., by RRC, DCI bitmap, etc. or by a number of retransmissions plus NDI.
  • Figure 5 illustrates the operation of a base station 302 and a UE 308 in accordance with at least some aspects of Embodiment 2 described above.
  • the base station 302 optionally determines (e.g., decides) to enable non-contiguous bundling for a specific HARQ process(es) (step 500). For example, the base station 302 may determine to enable non-contiguous bundling for a HARQ process(es) for which HARQ mechanism(s) have been disabled. Notably, the HARQ process(es) for which non-contiguous bundling is enabled is a subset of all configured HARQ processes. The base station 302 provides an indication to the UE 302 of the HARQ process(es) for which bundling is enabled (step 502).
  • This indication can be provided to the UE 308 in any suitable manner such as e.g. indicated dynamically in the received DCI using a bit indication, indicated using a specific RNTI(s), indicated using a MAC CE, indicated semi-static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the base station 302 also provides, to the UE 308, an indication of the number of bundles to use and/or a non-contiguous bundling pattern(s) for the indicated HARQ process(es) (step 504).
  • the UE 308 receives the indication in step 502 and optionally the indication in step 504 and, based on the received indication(s), determines that non-contiguous bundling is enabled for the specific indicated HARQ process(es) (step 506).
  • the UE 308 and the base station 312 then perform DL/UL data transmission/reception associated with the indicated HAR process(es) with non-contiguous bundling enabled (step 508).
  • the base station 302 may determine to configure a first HARQ process for contiguous bundling and second HARQ process for non-contiguous bundling.
  • the base station 302 can, for example, indicate to the UE 308 in step 502 that bundling is enabled for both the first and second HARQ processes.
  • the base station 302 may provide a further indication to the UE 308 that the bundling for the second HARQ process is non-contiguous, e.g., by indicating a respective non-contiguous bundling pattern to the UE 308, e.g., in step 504.
  • contiguous bundling is used for the first HARQ process and non-contiguous bundling is used for the second HARQ process.
  • the current NR specification requires generating possibly different redundancy versions of the TB, and a version of the TB is transmitted at each transmission occasion from the total of aggregationF actor transmission occasions in a bundle.
  • the codeword could be directly generated, rate matched, modulated and mapped to all the resource elements from the available symbols assigned to the TB.
  • the codeword for the TB is generated, rate matched, and the corresponding bits are modulated and mapped to the available resource elements.
  • a HARQ process timer for bundling of (non-) contiguous TBs is provided. Similar to bundling of X non-contiguous TBs for a certain HARQ process (e.g., identified by a certain HARQ process ID), the UE keeps monitoring for a specific HARQ process ID while the HARQ process timer is running. When the timer expires, the UE uses the received bundle of TBs, with possibly different redundancy versions, to decode the TB. The timer could be connected to each HARQ process, and the network (e.g. the base station 302) should not reuse the same HARQ process ID until the timer has expired or if the NDI is toggled.
  • the network e.g. the base station 302
  • HARQ feedback is turned on or off (i.e., regardless of whether HARQ mechanism(s) are deactivated for the respective HARQ process).
  • Figure 6 illustrates the operation of a base station 302 and a UE 308 in accordance with at least some aspects of Embodiment 3 described above.
  • the base station 302 optionally determines (e.g., decides) to enable (non-contiguous) bundling for a specific HARQ process(es) (step 600). For example, the base station 302 may determine to enable (non-contiguous) bundling for a HARQ process(es) for which HARQ mechanism(s) have been disabled. Notably, the HARQ process(es) for which (non-contiguous) bundling is enabled is a subset of all configured HARQ processes. The base station 302 provides an indication to the UE 302 of the HARQ process(es) for which bundling is enabled (step 602).
  • the base station 302 provides an indication to the UE 302 of the HARQ process(es) for which bundling is enabled (step 602).
  • This indication can be provided to the UE 308 in any suitable manner such as e.g. indicated dynamically in the received DCI using a bit indication, indicated using a specific RNTI(s), indicated using a MAC CE, indicated semi-static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the base station 302 also provides, to the UE 308, an indication HARQ process timer value(s) for the HARQ process(es) for which bundling is enabled (step 604).
  • This indication may be provided to the UE 308 in any suitable manner such as, e.g., dynamically in the received DCI using a bit indication, using a specific RNTI(s), using a MAC CE, using semi-static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the UE 308 receives the indication in step 602 and optionally the indication in step 604 and, based on the received indication(s), determines that bundling is enabled for the specific indicated HARQ process(es) (step 606).
  • the UE 308 starts a HARQ process timer(s) for the indicated HARQ process(es), where the HARQ process timer(s) is set to a value(s) indicated by the base station 302 in step 604 or set to value(s) that are otherwise defined for configured.
  • the UE 308 and the base station 312 then perform DL/UL data transmission/reception associated with the indicated HAR process(es) with bundling enabled while the respective HARQ process timer(s) is running (step 508).
  • RRC is used to provide the indication to enable bundling for a specific HARQ process(es).
  • Two examples of RRC configuration are as follows:
  • the RRC configuration can include a table that includes, for each configured HARQ process: (a) the number of repetitions (e.g., the aggregation factor for the HARQ process), (b) an indication of whether HARQ is disabled or not for the specific HARQ process, and/or (c) an indication as to whether non-contiguous bundling is allowed for the HARQ process.
  • the number of repetitions e.g., the aggregation factor for the HARQ process
  • an indication of whether HARQ is disabled or not for the specific HARQ process e.g., the aggregation factor for the HARQ process
  • an indication as to whether non-contiguous bundling is allowed for the HARQ process.
  • the RRC configuration can include configuration for only the specific HARQ process(es) for which HARQ mechanism(s) have been disabled. Instead of indicating for which HARQ process IDs HARQ has been turned off, this can be implicitly determined.
  • a combination of RRC and MAC CE or a combination of RRC and DCI is used to configure bundling for a specific HARQ process(es).
  • RRC configures a set of bundling and HARQ on/off states for given HARQ process or common to all HARQ processes.
  • MAC CE or DCI may then indicate which of the preconfigured states becomes active/deactive.
  • Option 1 is that each HARQ process is configured with N possible states, where one state can mean bundling is assumed and no HARQ, or bundling is assumed and HARQ is also enabled.
  • Option 2 the configuration state is common for all HARQ processes and MAC CE or DCI indicated which state is assumed for the UE.
  • the states may be indexed such that those can be referred by MAC CE or predefined ordering is assumed. E.g. first bit in MAC CE refers to first state in the list of configured states.
  • a combination of RRC and RNTI to activate/deactivate bundling for a specific HARQ process(es) is used.
  • DCI is used to configure bundling for a specific HARQ process(es).
  • the amount of bundling on each HARQ process is controlled by either signalling increase, decrease or maintain. As an example, if the current bundling number is 32 for HARQ process ID 4, then if MAC CE signals an increase on HARQ process ID then the bundling number is increased to 64.
  • the UE can try to decode the data after each received TB within the bundle. In case the UE is able to decode the data, it can discard future TBs within the same bundle (same HARQ process ID), this will lead to energy savings at the UE side.
  • the UE can feedback to the NW indicating successful transmission of the TB and thus NW could terminate transmission early (instead of blindly sending aggregation Factor times of the TB).
  • the UE can feedback the decoding information of the bundle to enable the network to set optimal TB sizes, bundling parameters, MCS, in order to optimize the resource utilization for future communication with said UE.
  • the UE reported feedback could be, e.g.:
  • a parameter for logical channel prioritization, LCP, that can be indicated in e.g. a grant is provided. If this indication is included, the UE may only include data from specific LCH that are allowed to send data on HARQ
  • Example: HARQ process IDs 4 and 5 are configured to not send HARQ feedback.
  • the LCP in the is then only allowed to include data from LCHs that indicates that data from these buffers are ok to be sent without feedback.
  • Figure 7 illustrates the operation of a base station 302 and a UE 308 in accordance with at least some aspects of Embodiment 6. Optional steps are represented with dashed lines.
  • the base station 302 optionally determines (e.g., decides) an indication for mapping data (step 700).
  • the base station 302 provides to the UE 302 of an indication for mapping data that can be sent on one or more of specific HARQ processes (step 702).
  • This indication can be provided to the UE 308 in any suitable manner such as e.g. in a grant, indicated dynamically in the received DCI using a bit indication, indicated using a specific RNTI(s), indicated using a MAC CE, indicated semi-static signaling such as, e.g., Radio Resource Control (RRC) signaling, or the like.
  • RRC Radio Resource Control
  • the UE 308 receives the indication in step 702 (step 704).
  • the UE 308 and the base station 312 then perform transmission/reception of a transmission based on the received indication (step 706).
  • a repetition is configured for a certain logical channel with a certain logical channel priority. This can be configured directly by RRC in LogicalChannelConfig IE with a parameter giving the repetition order.
  • MAC entity when receiving MAC SDU from such logical channel, MAC entity forms the configured number of MAC PDUs of the same MAC SDU.
  • FIG. 8 is a schematic block diagram of a radio access node 800 according to some embodiments of the present disclosure.
  • the radio access node 800 may be, for example, the base station 302 or the combination of the base station 302 and the base station antenna 304 described above.
  • the radio access node 800 includes a control system 802 that includes one or more processors 804 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 806, and a network interface 808.
  • the one or more processors 804 are also referred to herein as processing circuitry.
  • the radio access node 800 includes one or more radio units 810 that each includes one or more transmitters 812 and one or more receivers 814 coupled to one or more antennas 816.
  • the radio units 810 may be referred to or be part of radio interface circuitry.
  • the radio unit(s) 810 is external to the control system 802 and connected to the control system 802 via, e.g., a wired connection (e.g., an optical cable).
  • the control system 802 may be implemented in the base station 302
  • the radio unit(s) 810 and antennas 816 may be implemented in the base station antenna 304.
  • the radio unit(s) 810 and potentially the antenna(s) 816 are integrated together with the control system 802.
  • the one or more processors 804 operate to provide one or more functions of a radio access node 800 (e.g., one or more functions of the base station, eNB, or gNB) as described herein.
  • the function(s) are implemented in software that is stored, e.g., in the memory 806 and executed by the one or more processors 804.
  • FIG. 9 is a schematic block diagram that illustrates a virtualized embodiment of the radio access node 800 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures.
  • a“virtualized” radio access node is an implementation of the radio access node 800 in which at least a portion of the functionality of the radio access node 800 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)).
  • the radio access node 800 includes one or more processing nodes 900 coupled to or included as part of a network(s) 902 via the network interface 808.
  • Each processing node 900 includes one or more processors 904 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 906, and a network interface 908.
  • the radio access node 800 includes the control system 802 and/or the radio unit(s) 810, depending on the particular implementation.
  • functions 910 of the radio access node 800 described herein e.g., functions of the base station, eNB, or gNB described herein
  • functions 910 of the radio access node 800 described herein are implemented at the one or more processing nodes 900 or distributed across the control system 802 and the one or more processing nodes 900 in any desired manner.
  • some or all of the functions 910 of the radio access node 800 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual
  • control system 802 may not be included, in which case the radio unit(s) 810 can communicate directly with the processing node(s) 900 via an appropriate network interface(s).
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node 800 or a node (e.g., a processing node 900) implementing one or more of the functions 910 of the radio access node 800 in a virtual environment according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 10 is a schematic block diagram of the radio access node 800 according to some other embodiments of the present disclosure.
  • the radio access node 800 includes one or more modules 1000, each of which is implemented in software.
  • the module(s) 1000 provide the functionality of the radio access node 800 described herein. This discussion is equally applicable to the processing node 900 of Figure 9 where the modules 1000 may be
  • FIG. 1 1 is a schematic block diagram of a UE 1 100 according to some embodiments of the present disclosure.
  • the UE 1 100 includes one or more processors 1 102 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1 104, and one or more transceivers 1 106 each including one or more transmitters 1 108 and one or more receivers 1 1 10 coupled to one or more antennas 1 1 12.
  • processors 1 102 e.g., CPUs, ASICs, FPGAs, and/or the like
  • memory 1 104 e.g., RAM, RAM, and/or the like
  • transceivers 1 106 each including one or more transmitters 1 108 and one or more receivers 1 1 10 coupled to one or more antennas 1 1 12.
  • the transceiver(s) 1 106 includes radio-front end circuitry connected to the antenna(s) 1 1 12 that is configured to condition signals communicated between the antenna(s) 1 1 12 and the processor(s) 1 102, as will be appreciated by on of ordinary skill in the art.
  • the processors 1 102 are also referred to herein as processing circuitry.
  • the transceivers 1 106 are also referred to herein as radio circuitry.
  • the functionality of the UE 1 100 i.e., the functionality of the UE described above may be fully or partially implemented in software that is, e.g., stored in the memory 1 104 and executed by the processor(s) 1 102.
  • the UE 1 100 may include additional components not illustrated in Figure 1 1 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the UE 1 100 and/or allowing output of information from the UE 1 100), a power supply (e.g., a battery and associated power circuitry), etc.
  • user interface components e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the UE 1 100 and/or allowing output of information from the UE 1 100
  • a power supply e.g., a battery and associated power circuitry
  • a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 1 100 according to any of the embodiments described herein is provided.
  • a carrier comprising the aforementioned computer program product is provided.
  • the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
  • FIG 12 is a schematic block diagram of the UE 1 100 according to some other embodiments of the present disclosure.
  • the UE 1 100 includes one or more modules 1200, each of which is implemented in software.
  • the module(s) 1200 provide the functionality of the UE 1 100 described herein.
  • a communication system includes a telecommunication network 1300, such as a 3GPP-type cellular network, which comprises an access network 1302, such as a RAN, and a core network 1304.
  • the access network 1302 comprises a plurality of base stations 1306A, 1306B, 1306C, such as NBs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1308A, 1308B, 1308C.
  • Each base station 1306A, 1306B, 1306C is connectable to the core network 1304 over a wired or wireless connection 1310.
  • a first UE 1312 located in coverage area 1308C is configured to wirelessly connect to, or be paged by, the corresponding base station 1306C.
  • a second UE 1314 in coverage area 1308A is wirelessly connectable to the corresponding base station 1306A. While a plurality of UEs 1312, 1314 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1306.
  • the telecommunication network 1300 is itself connected to a host computer 1316, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm.
  • the host computer 1316 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections 1318 and 1320 between the telecommunication network 1300 and the host computer 1316 may extend directly from the core network 1304 to the host computer 1316 or may go via an optional intermediate network 1322.
  • the intermediate network 1322 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1322, if any, may be a backbone network or the Internet; in particular, the intermediate network 1322 may comprise two or more sub-networks (not shown). [0131]
  • the communication system of Figure 13 as a whole enables
  • the connectivity may be described as an Over-the-Top (OTT) connection 1324.
  • the host computer 1316 and the connected UEs 1312, 1314 are configured to communicate data and/or signaling via the OTT connection 1324, using the access network 1302, the core network 1304, any intermediate network 1322, and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 1324 may be transparent in the sense that the participating
  • the base station 1306 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1316 to be forwarded (e.g., handed over) to a connected UE 1312. Similarly, the base station 1306 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1312 towards the host computer 1316.
  • a host computer 1402 comprises hardware 1404 including a communication interface 1406 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1400.
  • the host computer 1402 further comprises processing circuitry 1408, which may have storage and/or processing capabilities.
  • the processing circuitry 1408 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the host computer 1402 further comprises software 1410, which is stored in or accessible by the host computer 1402 and executable by the processing circuitry 1408.
  • the software 1410 includes a host application 1412.
  • the host application 1412 may be operable to provide a service to a remote user, such as a UE 1414 connecting via an OTT connection 1416 terminating at the UE 1414 and the host computer 1402. In providing the service to the remote user, the host application 1412 may provide user data which is transmitted using the OTT connection 1416.
  • the communication system 1400 further includes a base station 1418 provided in a telecommunication system and comprising hardware 1420 enabling it to communicate with the host computer 1402 and with the UE 1414.
  • the hardware 1420 may include a communication interface 1422 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1400, as well as a radio interface 1424 for setting up and maintaining at least a wireless connection 1426 with the UE 1414 located in a coverage area (not shown in Figure 14) served by the base station 1418.
  • the communication interface 1422 may be configured to facilitate a connection 1428 to the host computer 1402.
  • connection 1428 may be direct or it may pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 1420 of the base station 1418 further includes processing circuitry 1430, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the base station 1418 further has software 1432 stored internally or accessible via an external connection.
  • the communication system 1400 further includes the UE 1414 already referred to.
  • the UE’s 1414 hardware 1434 may include a radio interface 1436 configured to set up and maintain a wireless connection 1426 with a base station serving a coverage area in which the UE 1414 is currently located.
  • the hardware 1434 of the UE 1414 further includes processing circuitry 1438, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions.
  • the UE 1414 further comprises software 1440, which is stored in or accessible by the UE 1414 and executable by the processing circuitry 1438.
  • the software 1440 includes a client application 1442.
  • the client application 1442 may be operable to provide a service to a human or non-human user via the UE 1414, with the support of the host computer 1402.
  • the executing host application 1412 may communicate with the executing client application 1442 via the OTT connection 1416 terminating at the UE 1414 and the host computer 1402.
  • the client application 1442 may receive request data from the host application 1412 and provide user data in response to the request data.
  • the OTT connection 1416 may transfer both the request data and the user data.
  • the client application 1442 may interact with the user to generate the user data that it provides.
  • the host computer 1402, the base station 1418, and the UE 1414 illustrated in Figure 14 may be similar or identical to the host computer 1316, one of the base stations 1306A, 1306B, 1306C, and one of the UEs 1312, 1314 of Figure 13, respectively.
  • the inner workings of these entities may be as shown in Figure 14 and independently, the surrounding network topology may be that of Figure 13.
  • the OTT connection 1416 has been drawn abstractly to illustrate the communication between the host computer 1402 and the UE 1414 via the base station 1418 without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the network
  • the infrastructure may determine the routing, which may be configured to hide from the UE 1414 or from the service provider operating the host computer 1402, or both. While the OTT connection 1416 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 1426 between the UE 1414 and the base station 1418 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1414 using the OTT connection 1416, in which the wireless connection 1426 forms the last segment. More precisely, the teachings of these embodiments may improve e.g., data rate, latency, and/or power consumption and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1416 between the host computer 1402 and the UE 1414, in response to variations in the measurement results.
  • measurement procedure and/or the network functionality for reconfiguring the OTT connection 1416 may be implemented in the software 1410 and the hardware 1404 of the host computer 1402 or in the software 1440 and the hardware 1434 of the UE 1414, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1416 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1410, 1440 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1416 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1418, and it may be unknown or imperceptible to the base station 1418. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer 1402’s measurements of throughput, propagation times, latency, and the like. The measurements may be
  • the software 1410 and 1440 causes messages to be transmitted, in particular empty or‘dummy’ messages, using the OTT connection 1416 while it monitors propagation times, errors, etc.
  • Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • step 1500 the host computer provides user data.
  • sub-step 1502 (which may be optional) of step 1500, the host computer provides the user data by executing a host application.
  • step 1504 the host computer initiates a transmission carrying the user data to the UE.
  • step 1506 (which may be optional)
  • the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 1508 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
  • Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • the transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • step 1700 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1702, the UE provides user data. In sub-step 1704 (which may be optional) of step 1700, the UE provides the user data by executing a client application. In sub-step 1706 (which may be optional) of step 1702, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user.
  • the UE initiates, in sub-step 1708 (which may be optional), transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • a method performed by a wireless device for mapping data to specific HARQ processes comprising at least one of:
  • WT406 transmitting/receiving (WT406) a transmission for the specific HARQ process based on the received indication.
  • a method performed by a base station for mapping data to specific HARQ processes comprising at least one of:
  • step WT400 determining (e.g., deciding) an indication for mapping data.
  • the method of embodiment 1 or 2 further comprising receiving (WT104), from the base station, an indication of a number of repetitions to use for bundling for the specific HARQ process.
  • a method performed by a wireless device for enabling bundling for a specific HARQ process comprising at least one of: receiving (402, 502, 602), from a base station, an indication that bundling of transport blocks is enabled for a specific HARQ process (or a specific subset of all configured HARQ processes); determining (406, 506, 606) that bundling is enabled for the specific HARQ process based on the received indication; and
  • the method of embodiment 1 wherein the specific HARQ process is a HARQ process for which HARQ mechanisms are at least partially deactivated. 3. The method of embodiment 1 or 2 further comprising receiving (404), from the base station, an indication of a number of repetitions to use for bundling for the specific HARQ process.
  • transmitting/receiving (408, 508, 610) the transmission for the specific HARQ process with bundling enabled comprises transmitting/receiving (610) the transmission for the specific HARQ process with bundling enabled while the timer is running.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving the indication via dynamic signaling (e.g., in a DCI message scheduling the transmission, in a MAC CE, by using a specific RNTI) or semi-static signaling (e.g., RRC signaling).
  • dynamic signaling e.g., in a DCI message scheduling the transmission, in a MAC CE, by using a specific RNTI
  • semi-static signaling e.g., RRC signaling
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving a DCI message scheduling the transmission, wherein the DCI message comprises a NDI field that is repurposed to provide the indication that bundling is enabled for the specific HARQ process.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving the indication via RRC signaling.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving indication via a combination of RRC signaling and dynamic signaling (e.g., MAC CE or DCI).
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving the indication via a combination of RRC signaling and a specific RNTI.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving a DCI message comprising the indication.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving a message to increase bundling (e.g., increase aggregation factor) for the specific HARQ process.
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving a message to decrease bundling (e.g., decrease aggregation factor) for the specific HARQ process.
  • a message to decrease bundling e.g., decrease aggregation factor
  • receiving the indication that bundling is enabled for the specific HARQ process comprises receiving a message to maintain bundling (e.g., maintain aggregation factor) for the specific HARQ process.
  • transmitting/receiving the transmission comprises transmitting/receiving the transmission via a satellite link.
  • a method performed by a base station for enabling bundling for a specific HARQ process comprising at least one of:
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending the indication via dynamic signaling (e.g., in a DCI message scheduling the transmission, in a MAC CE, by using a specific RNTI) or semi-static signaling (e.g., RRC signaling).
  • dynamic signaling e.g., in a DCI message scheduling the transmission, in a MAC CE, by using a specific RNTI
  • semi-static signaling e.g., RRC signaling
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending a DCI message scheduling the transmission, wherein the DCI message comprises a NDI field that is repurposed to provide the indication that bundling is enabled for the specific HARQ process.
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending the indication via RRC signaling.
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending indication via a combination of RRC signaling and dynamic signaling (e.g., MAC CE or DCI).
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending the indication via a combination of RRC signaling and a specific RNTI.
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending a DCI message comprising the indication.
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending a message to increase bundling (e.g., increase aggregation factor) for the specific HARQ process.
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending a message to decrease bundling (e.g., decrease aggregation factor) for the specific HARQ process.
  • decreasing bundling e.g., decrease aggregation factor
  • sending the indication that bundling is enabled for the specific HARQ process comprises sending a message to maintain bundling (e.g., maintain aggregation factor) for the specific HARQ process.
  • transmitting/receiving the transmission comprises transmitting/receiving the transmission via a satellite link.
  • a wireless device for deactivating HARQ mechanisms comprising:
  • processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • power supply circuitry configured to supply power to the wireless device.
  • a base station for deactivating HARQ mechanisms comprising:
  • processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • power supply circuitry configured to supply power to the base station.
  • an antenna configured to send and receive wireless signals
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • processing circuitry being configured to perform any of the steps of any of the Group A embodiments
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry;
  • a battery connected to the processing circuitry and configured to supply power to the UE.
  • a communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE;
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the communication system of the previous 2 embodiments further including the UE, wherein the UE is configured to communicate with the base station.
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.
  • a User Equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE;
  • the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of the Group A embodiments.
  • the cellular network further includes a base station configured to communicate with the UE.
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.
  • a communication system including a host computer comprising:
  • UE User Equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of the Group A embodiments.
  • the communication system of the previous embodiment further including the UE.
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • a method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.
  • the UE executing a client application
  • the LIE receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application
  • the user data to be transmitted is provided by the client application in response to the input data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • the communication system of the previous embodiment further including the base station.
  • the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • a method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

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 dispositif sans fil pour mapper des données avec des processus HARQ spécifiques. Le procédé consiste à : recevoir une indication qui mappe des données qui peuvent être envoyées sur un ou plusieurs processus HARQ spécifiques ; et émettre/recevoir une transmission pour le processus HARQ spécifique d'après l'indication reçue. L'invention concerne également un procédé mis en œuvre par une station de base pour mapper des données avec des processus HARQ spécifiques. L'invention concerne également un dispositif sans fil et une station de base permettant de mapper des données avec des processus HARQ spécifiques.
EP19839128.6A 2018-11-01 2019-11-01 Mappage de lch vec un id processus harq pour des réseaux non terrestres Pending EP3874647A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862754317P 2018-11-01 2018-11-01
PCT/IB2019/059405 WO2020089858A1 (fr) 2018-11-01 2019-11-01 Mappage de lch vec un id processus harq pour des réseaux non terrestres

Publications (1)

Publication Number Publication Date
EP3874647A1 true EP3874647A1 (fr) 2021-09-08

Family

ID=69174529

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19839128.6A Pending EP3874647A1 (fr) 2018-11-01 2019-11-01 Mappage de lch vec un id processus harq pour des réseaux non terrestres

Country Status (3)

Country Link
US (1) US20210385020A1 (fr)
EP (1) EP3874647A1 (fr)
WO (1) WO2020089858A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220158770A1 (en) * 2019-03-15 2022-05-19 Kt Corporation Method for performing communication by using non-terrestrial network, and device therefor
US20200396023A1 (en) * 2019-06-14 2020-12-17 Qualcomm Incorporated Downlink decoding feedback for hybrid automatic repeat request-less transmission modes
US11677509B2 (en) * 2020-02-21 2023-06-13 Qualcomm Incorporated Acknowledgment feedback techniques in wireless communications with large propagation delays
US11929831B2 (en) * 2020-03-11 2024-03-12 Qualcomm Incorporated Disabling hybrid automatic repeat request feedback
WO2022032189A1 (fr) * 2020-08-07 2022-02-10 Intel Corporation Système et procédé d'amélioration de la fiabilité dans des transmissions de multidiffusion nr et de planification de groupe dans des transmissions de multidiffusion nr à cellule unique
US20220045791A1 (en) * 2020-08-07 2022-02-10 Electronics And Telecommunications Research Institute Method and apparatus for retransmission using aggregation factor in communication network
CN116114320A (zh) * 2020-09-09 2023-05-12 鸿颖创新有限公司 用于非地面网络中的混合自动重传请求过程操作的方法及用户设备
WO2022099514A1 (fr) * 2020-11-11 2022-05-19 Oppo广东移动通信有限公司 Procédé et dispositif de communication sans fil
CN114614875B (zh) * 2020-12-07 2023-01-10 展讯半导体(南京)有限公司 重复传输次数确定方法与装置、终端和网络设备
KR20230124013A (ko) * 2021-01-14 2023-08-24 삼성전자주식회사 논리 채널의 사용 가능한 harq 프로세스를 설정하는방법 및 장치
WO2023216216A1 (fr) * 2022-05-13 2023-11-16 Lenovo (Beijing) Limited Désactivation de harq iot ntn pour un groupage harq et une planification multi-tb

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9621310B2 (en) * 2013-12-23 2017-04-11 Apple Inc. TTI bundling for downlink communication
CA3032474A1 (fr) * 2018-02-02 2019-08-02 Comcast Cable Communications, Llc Communications sans fil au moyen d'information de circulation

Also Published As

Publication number Publication date
US20210385020A1 (en) 2021-12-09
WO2020089858A1 (fr) 2020-05-07

Similar Documents

Publication Publication Date Title
US20210385020A1 (en) Lch mapping to harq process id for non-terrestrial networks
US20210391952A1 (en) Harq bundling procedure for non-terrestrial networks
US20220045803A1 (en) Adapting harq procedures for non-terrestrial networks
US11979222B2 (en) Systems and methods for timing adaptation for satellite communications
EP4038794B1 (fr) Construction de répertoires de codes harq avec activation/désactivation de rétroaction par processus de harq
US20210321353A1 (en) Systems and methods for uplink transmission timing
EP4046308B1 (fr) Systèmes et procédés de confirmation fiable d'ack/nack de ce mac
US10931409B2 (en) Configurable timing relationship and HARQ operational parameters
US20220070907A1 (en) Network node, ue and methods performed therein for handling communication
EP4236538A1 (fr) Procédé de réalisation d'une commutation de bwp par un terminal dans un système de communication sans fil, et dispositif associé
WO2021026849A1 (fr) Procédé, appareil et système pour transmettre des données
US20240171320A1 (en) Method, user equipment, and network node
WO2023210547A1 (fr) Procédé, équipement utilisateur et nœud de réseau
JP2021513764A (ja) 情報フィードバック方法及び装置、コンピュータ記憶媒体
EP4280504A1 (fr) Procédé par lequel un terminal transmet un signal de rétroaction dans un système de communication sans fil, et appareil associé

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20210507

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20230213

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20240314