Transport block across multiple slots for downlink transmission

Abstract

Mechanisms are provided for a user equipment (UE) to receive a Physical Downlink Shared Channel (PDSCH) transmission of a Transport Block (TB) across multiple slots. The UE may receive a configuration for a PDSCH transmission for a TB (TBoMS) across a plurality of slots, such as a first number of slots, over a downlink from the base station. The configuration may include an indication of the first number of time slots. The UE may also determine a transport block size (TBS) for the PDSCH transmission and allocate a second number of slots used by the UE to support the PDSCH transmission. Based on the TBS for the PDSCH transmission satisfying a condition, the processor may be configured to receive the PDSCH transmission for the TB across the second number of time slots, and decode the received PDSCH transmission.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. non-provisional patent application No. 18 / 129,658 filed on March 31, 2023, which claims the benefit of U.S. provisional patent application No. 63 / 334,922 filed on April 26, 2022, both of which are incorporated herein by reference in their entirety. Technical Field

[0003] The described aspects generally relate to a wireless communication system that includes a transport block (TB) spanning multiple time slots (TBoMS) for downlink transmissions.

[0004] Related fields

[0005] Wireless communication systems may include fifth generation (5G) systems, new radio (NR) systems, long term evolution (LTE) systems, non-terrestrial wireless networks (NTNs), combinations thereof, or some other wireless systems. In addition, wireless communication systems may support a wide range of use cases, such as enhanced mobile broadband (eMBB), massive machine type communications (mMTC), ultra-reliable and low latency communications (URLLC), and enhanced vehicle-to-everything communications (eV2X), among others. Large propagation delays may become a problem for many wireless communication systems. Summary of the invention

[0006] Some aspects of the present disclosure relate to apparatus and methods for implementing techniques for receiving a physical downlink shared channel (PDSCH) transmission of a transport block (TB) across multiple time slots by a user equipment (UE) from a base station. The received PDSCH transmission of TBs across multiple time slots can help enhance the technology to overcome challenges in wireless networks with large propagation delays. The implemented techniques can be applicable to many wireless systems, such as wireless communication systems based on 3rd Generation Partnership Project (3GPP) Release 15 (Rel-15), Release 16 (Rel-16), Release 17 (Rel-17), non-terrestrial wireless networks (NTNs), or other wireless networks.

[0007] Some aspects of the present disclosure relate to a UE. The UE may include a transceiver configured to enable wireless communication with a base station and a processor communicatively coupled to the transceiver. The processor may be configured to receive a configuration for PDSCH transmission of a TB (TBoMS) across multiple time slots (such as a first number of time slots) via a downlink from a base station. The configuration may include an indication of the first number of time slots. In some embodiments, the downlink from the base station may include a link from a satellite to the UE. In some embodiments, the configuration may include a time domain resource allocation (TDRA) table with an indication of the first number of time slots for PDSCH transmission. In some embodiments, the configuration for PDSCH transmission of TBs across a first number of time slots may also include an indication of a second repetition of PDSCH transmission of TBs across the first number of time slots. In some embodiments, the processor is configured to receive downlink control information (DCI) for scheduling PDSCH transmission via a downlink from a base station.

[0008] According to some aspects, the processor may also be configured to: determine a transport block size (TBS) for PDSCH transmission; and allocate a second number of time slots used by the UE to support PDSCH transmission, such as allocating the second number of time slots based on available time slots for the UE. Based on the TBS for PDSCH transmission satisfying the condition, the processor may be configured to receive PDSCH transmissions of TBs across a second number of time slots, decode the received PDSCH transmissions across the second number of time slots to obtain TBs, and transmit feedback to the base station based on the decoded PDSCH transmissions.

[0009] In some embodiments, the processor may be configured to: receive an indication from a base station that enables the UE to receive a PDSCH transmission of TBs across a second number of time slots, wherein the indication is included in the DCI or included in a time domain resource allocation (TDRA) table. In some embodiments, the processor may be configured to determine that the TBS for PDSCH transmission meets the condition based on the TBS being less than a predetermined size for a single code block or less than a predetermined number of bits. In some embodiments, the downlink from the base station may include a link from a satellite to the UE, and the processor may be configured to determine an indication to start receiving PDSCH transmission of TBs across a second number of time slots based on a distance between the UE and the satellite being greater than a threshold distance. In some embodiments, the second number of time slots may include a first time slot and a second time slot, wherein the first time slot may include a plurality of resource elements for PDSCH transmission, and the second time slot may include the same number of resource elements for PDSCH transmission.

[0010] The present invention is provided for the purpose of illustrating some aspects only, so as to provide an understanding of the subject matter described herein. Therefore, the above-mentioned features are only examples and should not be understood as narrowing the scope or essence of the subject matter in the present disclosure. Other features, aspects and advantages of the present disclosure will become apparent from the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present disclosure and, together with the description, further serve to explain the principles of the present disclosure and enable one skilled in the relevant art to make and use the present disclosure.

[0012] Figure 1 A non-terrestrial wireless network (NTN) including user equipment (UE) to receive physical downlink shared channel (PDSCH) transmissions of transport blocks (TBs) spanning multiple time slots is shown in accordance with some aspects of the present disclosure.

[0013] Figure 2 A block diagram of a UE including a transceiver and a processor according to some aspects of the present disclosure is shown.

[0014] Figure 3 An example process performed by a UE for receiving a PDSCH transmission of a TB spanning multiple slots according to some aspects of the present disclosure is shown.

[0015] FIG. 4A to FIG. 4C An example process performed by a UE for receiving a PDSCH transmission of a TB spanning multiple slots according to some aspects of the present disclosure is shown.

[0016] Figure 5 is an example computer system for implementing some aspects or portions of the disclosure provided herein.

[0017] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numerals indicate identical or functionally similar elements. Additionally, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0018] With the development of mobile communication networks, some wireless systems such as the fifth generation (5G) network or non-terrestrial wireless networks may have large propagation delays, higher propagation losses, weaker diffraction capabilities, and limited and shortened coverage for various reasons. Non-terrestrial wireless networks (NTNs) may refer to any network involving non-terrestrial flying objects. NTNs may include satellite communication networks, high altitude platform systems (HAPS), air-to-ground networks, low-altitude unmanned aerial vehicles (UAVs, also known as drones), or any other NTNs. Coverage enhancement techniques may be needed to address challenges in NTNs or other similar networks with large propagation delays or other problems.

[0019] In conventional wireless systems, uplink (UL) or downlink (DL) transmissions may be designed for time slots, which may be dynamically scheduled units or durations otherwise defined by a communication standard. There is usually no consistency requirement or coordination in different multiple time slots. A coverage enhancement technique that addresses the challenges caused by large propagation delays may coordinate UL or DL ​​transmissions across multiple time slots, such as physical downlink shared channel (PDSCH) transmissions of transport blocks (TBs) across multiple time slots (TBoMS). A transport block may be a data packet transferred between a medium access control (MAC) and a physical layer. The TB may be transferred downward at the transmitter and upward at the receiver. The TB may undergo physical layer processing at the transmitter before being mapped onto a PDSCH transmission for transmission across the air interface. A UE receiving data on a PDSCH transmission may determine a transport block size (TBS) before attempting to decode the data.

[0020] Certain aspects of the present disclosure provide mechanisms by which a UE receives PDSCH transmissions of TBs spanning multiple time slots.

[0021] Figure 1 An NTN 100 including a UE 101 for receiving PDSCH transmissions of TBs across multiple time slots according to some aspects of the present disclosure is shown. The NTN 100 is provided for illustration purposes only and is not intended to limit the disclosed aspects. When receiving PDSCH transmissions of TBs across multiple time slots, the techniques described herein for the NTN 100 may also be applicable to other wireless systems without satellites.

[0022] NTN 100 may include, but is not limited to, UE 101, base station 103, satellite 102, gateway 104, and core network 105. UE 101 communicates with satellite 102 via service link 111, and satellite 102 communicates with gateway 104 via feeder link 113. Service link 111 may include downlink 112 and uplink 114. Satellite 102 may include a network node or a transceiver for wireless communication. Various specific implementations of NTN 100 may exist. For example, base station 103 and gateway 104 may be integrated into one unit instead of separate components. Base station 103 and core network 105 may implement the function of a normal terrestrial wireless network without a satellite, and gateway 104 may implement the function between the terrestrial wireless network and satellite 102.

[0023] In some embodiments, the NTN 100 may have a transparent payload, where the base stations 103 are located on the ground. In some embodiments, the NTN 100 may have a regenerative payload, when the base stations 103 may be located on the satellite 102. There may be multiple satellites carrying base stations that communicate with each other. There may be other network entities not shown, such as network controllers, relay stations. The NTN may be referred to as a wireless network, a wireless communication system, or some other name known to those of ordinary skill in the art.

[0024] In some embodiments, NTN 100 may be an NTN with non-terrestrial flying objects (e.g., satellite 102). In some embodiments, NTN 100 may include a satellite communication network including satellite 102, HAPS, or an air-to-ground network or UAV. Multiple satellites may exist in NTN 100. Satellite 102 may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, or a synchronous (GSO) earth orbit (GEO) satellite. NTN 100 may be a HAPS, which may be an airborne platform including an airplane, a hot air balloon, and an airship. For example, NTN 100 may include an international mobile communication base station, referred to as a HIBS. The HIBS system may provide mobile services in the same transmission frequency used by a land mobile network. NTN 100 may be an air-to-ground network for providing in-flight connectivity for an airplane by utilizing a ground station, which plays a role similar to a base station in a land mobile network. NTN 100 may also be a mobile low-altitude UAV.

[0025] In some embodiments, satellite 102 may be a GEO satellite deployed at an altitude of 35786 km and characterized by slow movement around its orbital position relative to a point on the earth. Compared to terrestrial cellular systems, GEO satellite-based communication networks have large propagation delays and high propagation losses that must be considered in the overall design of the satellite network. Additionally or alternatively, satellite 102 may be a LEO satellite at an altitude of 300-3000 km. In some embodiments, satellite 102 may communicate with UE 101 on various frequency bands, such as 1610-1618.725 MHz UL (L band) and 2483.5-2500 MHz DL (S band). There may be power flux density (PFD) limitations on the S band. For example, for the S band 2483.5-2500 MHz DL for mobile satellite services, the GSO satellite 102 may have a PFD: P = -146 dB (W / m at 4 kHz) 2 ) and P = -128dB (W / m 2 ), where r = 0.5. In addition, the non-GSO satellite 102 may have a PFD of: P = -144 dB (W / m 2 ) and at 1MHz it is -126dB(W / m 2 ), where r = 0.65.

[0026] According to some aspects, base station 103 can be a fixed station or a mobile station. In some embodiments, base station 103 can be located on satellite 102. Base station 103 can also be referred to as other names, such as base transceiver system (BTS), access point (AP), transmit / receive point (TRP), evolved node B (eNB), next generation node B (gNB), 5G node B (NB) or some other equivalent terms.

[0027] According to some aspects, UE 101 may be fixed or mobile. UE 101 may be a handheld terminal or a very small aperture terminal (VSAT), which is equipped with a parabolic antenna and is typically mounted on a building or a vehicle. UE 101 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop, a desktop computer, a cordless phone, a wireless local loop station, a tablet computer, a camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry such as a smart ring or smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component, a smart meter, an industrial manufacturing equipment, a global positioning system device, an Internet of Things (IoT) device, a machine type communication (MTC) device, an evolution or enhancement of a machine type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc.

[0028] According to some aspects, it can be based on Figure 2 The block diagram shown is used to implement UE 101. Figure 2 , UE 101 may have an antenna panel 217, which includes one or more antenna elements to form various transmit beams, such as beam 213, which are coupled to transceiver 203 and controlled by processor 209. Transceiver 203 and antenna panel 217 (using beam 213) can be configured to enable wireless communication in a wireless network. In detail, transceiver 203 may include radio frequency (RF) circuit 216, transmit circuit 212, and receive circuit 214. RF circuit 216 may include multiple parallel RF chains, which are used to perform one or more of the transmit or receive functions, each RF chain is connected to one or more antenna elements in the antenna panel. In addition, processor 209 is communicatively coupled to memory 201, which is further coupled to transceiver 203. Various data may be stored in memory 201.

[0029] In some embodiments, the memory 201 may store a configuration 121 for a PDSCH transmission 131 of a TB (TBoMS) across a plurality of time slots, such as a first number of time slots, received via a downlink 112 from a satellite 102, which is also part of a downlink from a base station 103 to a UE 101. The configuration 121 may include an indication of a first number of time slots used for the PDSCH transmission. In some embodiments, the configuration 121 may include a time domain resource allocation (TDRA) table 123 with an indication 125 of a first number of time slots used for the PDSCH transmission. The first number of time slots may be greater than 1, which means that a plurality of time slots are used in the PDSCH transmission of the TB. The configuration 121 may also include an indication 127 of a second repetition of the PDSCH transmission 131 of the TB across the first number of time slots.

[0030] In some embodiments, the memory 201 may store a transport block size (TBS) 221 for the PDSCH transmission 131, which may be determined by the processor 209. The processor 209 may also determine a second number 223 of time slots used by the UE 101 to support the PDSCH transmission. The memory 201 may also store a condition 225, which may be a condition compared to a predetermined size or a predetermined number of bits for a single code block. Based on the TBS 221 for the PDSCH transmission 131 satisfying the condition 225 and the second number 223 of time slots being greater than 1, the processor 209 may receive a PDSCH transmission 131 of TBs spanning the second number 223 of time slots. The second number 223 of time slots may be determined based on the available time slots for the UE 101.

[0031] In some embodiments, a time slot may be used as a dynamic scheduling unit. In addition, some wireless systems may support transmission based on a micro-time slot (a portion of a time slot) as the minimum scheduling unit. The number of OFDM symbols in each time slot may be fixed, such as 14 with a normal cyclic prefix (CP) and 12 with an extended CP. In LTE, the number of time slots in each subframe may be fixed to 2. In NR, the number of time slots in each subframe varies with parameter sets (increases with subcarrier spacing). In some embodiments, a time slot may have a length or duration of 0.5 ms, while some subframes may have a length or duration of 1 ms. Time slots may be classified as downlink (all symbols dedicated to downlink) or uplink (all symbols dedicated to uplink) or mixed uplink and downlink transmissions.

[0032] In some embodiments, memory 201 may include instructions that, when executed by processor 209, perform the operations described herein, for example, Figure 3The operations for receiving a PDSCH transmission for a TB spanning multiple time slots by a UE are described in process 300 in . Alternatively, the processor 209 may be "hard coded" to receive a PDSCH transmission for a TB spanning multiple time slots as described herein.

[0033] Figure 3 An example process 300 is shown for receiving a PDSCH transmission of a TB across multiple time slots performed by a UE according to some aspects of the present disclosure. Figure 3 As shown, process 300 may be performed by UE 101 .

[0034] At 301, UE 101 may receive, via a downlink from a base station, a configuration for PDSCH transmissions for TBs spanning a first number of time slots, wherein the configuration may include an indication of a first number of time slots greater than 1. For example, Figure 1 to Figure 2 As shown, UE 101 may receive a configuration 121 for a PDSCH transmission 131 across multiple time slots via a downlink from base station 103. Configuration 121 may include an indication 125 of a first number of time slots for PDSCH transmission, which may be included in TDRA table 123. In some embodiments, UE 101 may receive a DCI scheduling PDSCH transmission 131 via a downlink from the base station.

[0035] At 303, UE 101 may determine a TBS for PDSCH transmission. Figure 1 to Figure 2 As shown, UE 101 may determine TBS 221 for PDSCH transmission 131 .

[0036] At 305, UE 101 may determine a second number of time slots used by the UE to support PDSCH transmissions. Figure 1 to Figure 2 As shown, UE 101 may determine a second number 223 of time slots used by UE 101 to support PDSCH transmission 131. The second number 223 of time slots may be less than the first number of time slots indicated by configuration 121. The second number 223 of time slots may be determined based on available time slots for the UE.

[0037] At 307, based on the TBS for the PDSCH transmission satisfying the condition, UE 101 may receive the PDSCH transmission across the TBs of the second number of time slots. Figure 1 to Figure 2 As shown, based on the TBS 221 for PDSCH transmission satisfying the condition 225 , the UE 101 may receive the PDSCH transmission 131 across the TBs of the second number 223 of time slots.

[0038] At 308, UE 101 may decode the received PDSCH transmission across the second number of time slots to obtain TBs. Figure 1 to Figure 2 As shown, UE 101 may decode received PDSCH transmission 131 across a second number 223 of time slots to obtain TBs.

[0039] At 309, UE 101 may transmit feedback to the base station based on the decoded PDSCH transmission. Figure 1 to Figure 2 As shown, UE 101 transmits feedback to the base station based on the decoded PDSCH transmission.

[0040] There may be other operations performed by UE 101. In some embodiments, UE 101 may receive an indication from base station 103 that enables UE 101 to receive PDSCH transmission 131 for TBs spanning a second number 223 of time slots, wherein the indication is included in a DCI or TDRA table. In some embodiments, UE 101 may determine that TBS 221 for PDSCH transmission 131 satisfies condition 225 based on TBS 221 being less than a predetermined size for a single code block or less than a predetermined number of bits. In some embodiments, a downlink from base station 103 to UE 101 may include a link from satellite 102 to UE 101, and UE 101 may determine an indication to begin receiving PDSCH transmission 131 for TBs spanning a second number 223 of time slots based on a distance between UE 101 and satellite 102 being greater than a threshold distance. In some embodiments, the second number 223 of time slots may include a first time slot and a second time slot, wherein the first time slot may include a plurality of resource elements for PDSCH transmission and the second time slot may include the same number of resource elements for PDSCH transmission.

[0041] FIG. 4A to FIG. 4C Example processes performed by a UE for receiving PDSCH transmissions of TBs across multiple slots according to some aspects of the present disclosure are shown, for example, process 400, process 410, process 420. Process 400, process 410, and process 420 may be examples of process 300, described in more, less, or different details.

[0042] Process 400 Figure 4A is shown as a general process without showing the tests that satisfy the conditions or Figure 3 Determination of the second number of time slots, step 305 and step 307 are shown.

[0043] At 401, UE 101 may receive a configuration for PDSCH transmissions for TBs across multiple time slots. The configuration may be a TDRA table including the number of time slots (N) for a single TB transmission, such as Table 1 shown below, where N may be a value such as {2, 4, 8}. The TDRA table may also include the number of repetitions (M) for PDSCH transmissions, where M may be M<=16. In some embodiments, M may be configured and used independently of N. In some embodiments, there may be some restrictions on the number N and M, such as M*N<=32. The base station 103 may modify information elements for PDSCH, such as PDSCH-TimeDomainResourceAllocation, to indicate such a TDRA table.

[0044] Table 1

[0045]

[0046]

[0047] At 403, UE 101 may receive DCI for scheduling downlink data transmission with TB (TBoMS) across multiple time slots. The TDRA table entry may indicate N>1 time slots allocated for TBoMS, which may apply to both dynamically granted PDSCH and semi-persistently scheduled (SPS) PDSCH.

[0048] At 405, UE 101 may receive and decode PDSCH transmissions across multiple time slots, where the multiple time slots may be indicated by the TDRA table. Therefore, this means that UE 101 may support the number of multiple time slots indicated by the TDRA table. UE 101 may perform rate matching by concatenating bits within a single repetition. UE 101 may also perform rate matching based on a redundancy version (RV) sequence within multiple repetitions.

[0049] In some embodiments, the available number of resource elements (REs) for PDSCH transmission may be different across multiple time slots. In some embodiments, at the resource element (RB) level, the RB may overlap with "reserved resources" such as synchronization signal blocks (SSBs) and CORESETs. Rate matching may be performed based on SSB periodicity, according to RB or SSB mode, and rate matching is performed around "reserved resources", SSBs or CORESETs. In some embodiments, at the resource element (RE) level, the RE may overlap with the channel state information reference signal (CSI-RS), and the PDSCH may be punctured by zero power (ZP)-CSI-RS.

[0050] In some embodiments, for the purpose of rate matching, the index of the starting coded bit of each of the multiple time slots used for PDSCH transmission can be predetermined before the TBoMS transmission begins. In some embodiments, the number (X) of rate matching output bits for PDSCH transmission can be the same across time slots. The number X can be determined based on the first time slot of the TBoMS used for PDSCH transmission. In addition and alternatively, the number X can be determined based on the deduction of the configured overhead of the TBoMS used for PDSCH transmission. When determining the value of X, some configured overhead (e.g., Y bits / RB) can be deducted without checking the actual RB / RE level overlap with "reserved resources", SSB, CORESET, CSI-RS, etc. In some embodiments, the number X can be determined based on the time slot with the minimum number of PDSCH resources. If the available number of REs for PDSCH transmission in the time slot is greater than the number X, the rate matching output bits for the time slot are repeated. Therefore, the second number of time slots includes a first time slot and a second time slot, wherein the first time slot includes a plurality of rate matching output bits for PDSCH transmission, and the second time slot includes the same number of rate matching output bits for PDSCH transmission. If the available number of REs for PDSCH transmission in the time slot is less than the number X, the remaining rate matching output bits may not be transmitted in the time slot. In some embodiments, the number of rate matching output bits for PDSCH transmission may be different across different multiple time slots. The number of rate matching output bits (X) for PDSCH transmission may be determined by each time slot for TBoMS, depending on the actual overlap with "reserved resources", SSB and CORESET. In addition, bit interleaving may be performed per TB or per time slot. In some embodiments, the index of the starting coded bit of each time slot may be dynamically determined before each TBoMS transmission time slot begins, and bit interleaving may be performed per time slot. In some embodiments, TBoMS may be transmitted repeatedly. The number of repetitions of TBoMS may be bounded, for example, by 16. In some embodiments, the number of repetitions of TBoMS is independently configured according to the number of time slots of each TBoMS. In some embodiments, the upper limit of the number of TBoMS repetitions is combined with the number of time slots per TBoMS, for example, the upper limit of the product of these two numbers is 32. In one embodiment, the redundancy version (RV) can be cyclic across TBoMS repetitions. In another embodiment, the RV can be fixed across TBoMS repetitions.

[0051] At 407, UE 101 may transmit a hybrid automatic repeat request (HARQ) feedback for the PDSCH transmission. In some embodiments, K1 may be based on the last time slot of the last PDSCH repetition. UE PDSCH processing time T' for TBoMS proc,1 Can be different from traditional Tproc,1 This allows more processing time for combining and decoding at low signal-to-noise ratios (SNR). The processing time may depend on the number of time slots N of a single TBoMS, the larger N is, the smaller T' is. proc,1 The bigger.

[0052] Process 410 in Figure 4B , where process 410 may include triggering a TBoMS for PDSCH transmission. In some embodiments, for a configuration provided by a base station for PDSCH transmission of a TB across multiple time slots, UE 101 may determine that PDSCH transmission of a TB across multiple time slots may not be enabled and reset it to transmit PDSCH transmission across only one time slot.

[0053] At 411, UE 101 may receive a configuration for PDSCH transmissions for TBs across multiple slots. The configuration may be a TDRA table including the number of slots (N) for a single TB transmission, such as Table 1 shown above.

[0054] At 413, UE 101 may receive a DCI for scheduling downlink data transmission with a TB across multiple time slots. The TDRA table entry may indicate N>1 time slots allocated to TBoMS. Such an entry N>1 may indicate that TBoMS for PDSCH transmission is enabled. Otherwise, TBoMS may be disabled. In some embodiments, the DCI may indicate the TDRA table entry to implicitly enable TBoMS. In some embodiments, if the TDRA table entry is not configured with "N", TBoMS is disabled. If the TDRA table entry is configured with "N", the DCI (e.g., format 1_1, 1_2) may additionally indicate whether TBoMS is activated. An additional bit in the DCI is used to indicate the activation of TBoMS. The code point of an existing DCI field (e.g., FDRA field) is used to indicate the activation of TBoMS. If enabled, the value N in the TDRA table is used. Otherwise, the value N in the TDRA table is ignored.

[0055] At 415, UE 101 may calculate TBS based on the indicated N value to enable TBoMS. Even though the configuration may include a TDRA table with an entry N configured to be greater than 1, meaning that base station 103 configures UE 101 to perform TBoMS, UE 101 may still determine to disable TBoMS. TBoMS may only be applied when transmission is limited to one code block (CB).

[0056] At 417, if the TDRA table entry has N>1, but the calculated TBS and the indicated modulation and coding scheme (MCS) imply multiple CB transmissions, the configuration of N>1 may be an error condition. In the case where TBoMS is used (i.e., N>1), UE 101 does not expect the calculated TBS to exceed the maximum TBS for a single CB transmission. In this case, UE 101 can ignore the N value in the TDRA table entry, reset N=1, and recalculate the TBS using only one time slot instead of multiple time slots. In some embodiments, TBoMS can be applied only when the TBS (including TB CRC) is less than A bits (e.g., 3840 bits). In some other embodiments, TBoMS can be applied only when the LDPC basis is used. Figure 2 TBoMS can only be applied when

[0057] In some embodiments, the triggering of TBoMS for PDSCH transmission can be performed in various ways. In some embodiments, the base station can trigger TBoMS based on a UE-specific Koffset value. When the Koffset value is greater than a threshold, the base station triggers TBoMS for PDSCH. In some embodiments, the UE can trigger TBoMS based on a UE-specific timing advance (TA) or full TA. When the UE-specific TA or full TA is greater than a threshold, the UE can request the base station to trigger TBoMS for PDSCH. The triggering can be performed via MAC CE or RRC signaling.

[0058] Process 420 Figure 4C , where process 420 may include allocating a second number of time slots used by the UE to support PDSCH transmission, where the second number of time slots may be different from the first number of time slots used to support PDSCH transmission of TBs across multiple time slots based on the configuration.

[0059] At 421, UE 101 may receive a configuration for PDSCH transmissions for TBs across multiple slots. The configuration may be a TDRA table including a first number (N) of slots for a single TB transmission, such as Table 1 shown above.

[0060] At 423, UE 101 may receive a DCI for scheduling a downlink data transmission with a TB spanning multiple time slots. The TDRA table entry may indicate N>1 time slots allocated to the TBoMS. In addition, the configuration may also indicate that the number of layers is greater than 1.

[0061] At 425, UE 101 may determine a TBS for PDSCH transmission. In some embodiments, the TBS may be determined based on a plurality of time slots:

[0062]

[0063] N RE =N*min(156,N R ′ E )*n PRB ;

[0064] N info =N RE *R*Q m *v

[0065] In some embodiments, when frequency domain response allocation (FDRA) is used, the same number of PRBs per symbol may be allocated across the timeslots used for TBoMS. In some embodiments, when TDRA is used, the number of timeslots allocated to a single TBoMS may be determined in various ways, such as based on the available timeslots for DL ​​transmissions. The available timeslots may be determined in two steps: determining the TDRA in the DCI and RRC configuration (such as the TDD UL / DL configuration), and then determining whether the DL timeslot is discarded according to the Release 15 / 16 / 17 discard rules. If the timeslot is discarded, it is still counted in the duplicate quantity. In some embodiments, the number of timeslots allocated to a single TBoMS may be determined as the physical timeslots after the initial DL timeslot, where the actual number of timeslots used for the TBoMS may be less than N, which is the configured number of timeslots used for the TBoMS. Accordingly, can be the same for all time slots, and N info Based on the number of REs determined in the first time slot, it is then scaled by the number of allocated time slots.

[0066] At 427, the UE 101 may determine the number of MIMO layers (rank) for the TBoMS. In some embodiments, the number of MIMO layers (rank) for the TBoMS is limited to 1. If the TDRA table entry has N>1, but the number of layers indicated by the DCI is greater than 1, it is an error condition. Based on the configuration, the UE 101 may treat N=1 (i.e., no TBoMS) or treat the number of layers=1.

[0067] At 429, UE 101 may calculate PDSCH resources and TBS based on the determined N value and number of layers. In some embodiments, UE 101 may ignore the N value in the TDRA table entry (or treat it as N=1) and recalculate the TBS. In some embodiments, UE 101 may treat the number of layers as 1 and recalculate the TBS. In some embodiments, UE 101 may select either of the above two methods to perform based on the configuration from base station 103.

[0068] For example, one or more computer systems (such as Figure 5The computer system 500 shown in the figure can be used to implement various aspects. The computer system 500 can be capable of performing the functions described herein for Figure 3 , FIG. 4A to FIG. 4C Any computer, such as the one described above, that operates processor 209, process 300, process 400, process 410, or process 420 Figure 1 and Figure 2 UE 101 or base station 103 shown. Computer system 500 includes one or more processors (also referred to as central processing units or CPUs), such as processor 504. Processor 504 is connected to a communication infrastructure 506 (e.g., a bus). Computer system 500 also includes user input / output devices 503, such as a monitor, keyboard, pointing device, etc., that communicate with communication infrastructure 506 through user input / output interface 502. Computer system 500 also includes main memory or primary storage 508, such as random access memory (RAM). Main memory 508 may include one or more levels of cache. Main memory 508 has control logic components (e.g., computer software) and / or data stored therein.

[0069] The computer system 500 may also include one or more secondary storage devices or memories 510. The secondary storage 510 may include, for example, a hard disk drive 512 and / or a removable storage device or drive 514. The removable storage drive 514 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0070] The removable storage drive 514 may interact with a removable storage unit 518. The removable storage unit 518 includes a computer usable or readable storage device having computer software (control logic) and / or data stored thereon. The removable storage unit 518 may be a floppy disk, a magnetic tape, a compact disk, a DVD, an optical storage disk, and / or any other computer data storage device. The removable storage drive 514 reads from and / or writes to the removable storage unit 518 in a well-known manner.

[0071] According to some aspects, secondary memory 510 may include other devices, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 500. Such devices, tools, or other methods may include, for example, a removable storage unit 522 and an interface 520. Examples of removable storage unit 522 and interface 520 may include a program cartridge and cartridge interface (such as found in video game devices), a removable memory chip (such as an EPROM or PROM) and an associated socket, a memory stick and USB port, a memory card and an associated memory card slot, and / or any other removable storage unit and associated interface.

[0072] In some examples, the main memory 508, the removable storage unit 518, and the removable storage unit 522 may store instructions that, when executed by the processor 504, cause the processor 504 to perform operations for a UE or a base station (e.g., Figure 1 and Figure 2 In some examples, the operations include: Figure 3 , FIG. 4A to FIG. 4C Those operations shown and described with respect to process 300 , process 400 , process 410 , or process 420 .

[0073] The computer system 500 may also include a communication or network interface 524. The communication interface 524 enables the computer system 500 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 528). For example, the communication interface 524 may allow the computer system 500 to communicate with the remote device 528 via a communication path 526, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, etc. Control logic components and / or data may be sent to and from the computer system 500 via the communication path 526. The operation of the communication interface 524 may be performed by a wireless controller and / or a cellular controller. The cellular controller may be a separate controller to manage communications according to different wireless communication technologies. The operations in the foregoing aspects may be implemented in various configurations and architectures. Thus, some or all of the operations in the foregoing aspects may be performed in hardware, software, or in both hardware and software. In some aspects, a tangible, non-transitory apparatus or article of manufacture includes a tangible, non-transitory computer usable or readable medium having stored thereon control logic components (software), also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 500, main memory 508, auxiliary memory 510, and removable storage units 518 and 522, and tangible articles of manufacture embodying any combination of the foregoing. Such control logic components, when executed by one or more data processing devices (such as computer system 500), cause such data processing devices to operate as described herein.

[0074] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Figure 5 The various aspects of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the various aspects may operate with software, hardware, and / or operating system implementations other than those described herein.

[0075] It should be understood that the Detailed Description section, rather than the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more but not all exemplary aspects of the present disclosure as contemplated by the inventors, and thus are not intended to limit the present disclosure or the appended claims in any way.

[0076] Although the present disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and essence of the present disclosure. For example, and without limiting the generality of this paragraph, the various aspects are not limited to the software, hardware, firmware and / or entities shown in the figures and / or described herein. In addition, the various aspects (whether or not explicitly described herein) have significant practicality for fields and applications outside the examples described herein.

[0077] Various aspects have been described herein by means of functional building blocks that illustrate specific implementations of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. As long as the specified functions and relationships (or their equivalents) are properly performed, alternative boundaries may be defined. In addition, alternative aspects may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0078] References herein to "one embodiment," "an embodiment," "an example embodiment," or similar phrases indicate that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is within the knowledge of those skilled in the relevant art to incorporate such feature, structure, or characteristic into other aspects, whether or not explicitly mentioned or described herein.

[0079] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary aspects, but should be defined only in accordance with the following claims and their equivalents.

[0080] For one or more embodiments or examples, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Examples section below. For example, circuitry associated with a thread device, router, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0081] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and privacy practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should only be done after receiving the user's informed consent. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that other entities with access to personal information data comply with the privacy policies and procedures of other entities. In addition, such entities may subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and privacy practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be advocated for different types of personal data in each country.

Claims

1. A method for performing wireless communication by a user equipment (UE), the method comprising: receiving, via a downlink from a base station, a configuration for a physical downlink shared channel (PDSCH) transmission for transport blocks (TBs) spanning a first number of time slots, wherein the configuration includes an indication of the first number of time slots; Determining a transport block size (TBS) for the PDSCH transmission; determining a second number of time slots used by the UE to support the PDSCH transmission; receiving the PDSCH transmission of the TBs spanning the second number of time slots based on the TBS for the PDSCH transmission satisfying a condition; decoding the received PDSCH transmission across the second number of time slots to obtain the TBs; and Feedback is transmitted to the base station based on the decoded PDSCH transmission.

2. The method according to claim 1, further comprising: Downlink control information (DCI) scheduling the PDSCH transmission is received through the downlink from the base station.

3. The method of claim 1, wherein the downlink from the base station comprises a link from a satellite to the UE.

4. The method of claim 1, wherein the configuration comprises a time domain resource allocation (TDRA) table having an indication of the first number of time slots used for the PDSCH transmission.

5. The method according to claim 1, further comprising: An indication is received from the base station to enable the UE to receive the PDSCH transmission of the TBs across the second number of time slots, wherein the indication is included in downlink control information (DCI) or in a time domain resource allocation (TDRA) table.

6. The method according to claim 1, further comprising: Based on the TBS being smaller than a predetermined size for a single code block or smaller than a predetermined number of bits, it is determined that the TBS used for the PDSCH transmission satisfies the condition.

7. The method of claim 1 , wherein the downlink from the base station comprises a link from a satellite to the UE, and the method further comprises: Based on the distance between the UE and the satellite being greater than a threshold distance, an indication to begin receiving the PDSCH transmission for the TBs spanning the second number of time slots is determined.

8. The method of claim 1, wherein the second number of time slots comprises a first time slot and a second time slot, wherein the first time slot comprises a plurality of rate matching output bits for the PDSCH transmission and the second time slot comprises the same number of rate matching output bits for the PDSCH transmission.

9. The method of claim 1, wherein the configuration for the PDSCH transmission of the TBs across the first number of time slots further comprises an indication to repeat the PDSCH transmission of the TBs across the first number of time slots for a second time.

10. The method of claim 1, wherein allocating the second number of time slots used by the UE to support the PDSCH transmission comprises allocating the second number of time slots based on available time slots for the UE.

11. A user equipment (UE), the UE comprising: a transceiver configured to enable wireless communication with a base station over a wireless network; as well as a processor communicatively coupled to the transceiver and configured to: receiving, via a downlink from the base station, a configuration for a physical downlink shared channel (PDSCH) transmission for transport blocks (TBs) spanning a first number of time slots, wherein the configuration includes an indication of the first number of time slots; Determining a transport block size (TBS) for the PDSCH transmission; allocating a second number of time slots used by the UE to support the PDSCH transmission; receiving the PDSCH transmission of the TBs spanning the second number of time slots based on the TBS for the PDSCH transmission satisfying a condition; decoding the received PDSCH transmission across the second number of time slots to obtain the TBs; and Feedback is transmitted to the base station based on the decoded PDSCH transmission.

12. The UE according to claim 11, wherein the processor is further configured to: Downlink control information (DCI) scheduling the PDSCH transmission is received through the downlink from the base station.

13. The UE of claim 11, wherein the downlink from the base station comprises a link from a satellite to the UE.

14. The UE of claim 11, wherein the configuration comprises a time domain resource allocation (TDRA) table with an indication of the first number of time slots used for the PDSCH transmission.

15. The UE according to claim 11, wherein the processor is further configured to: An indication is received from the base station to enable the UE to receive the PDSCH transmission of the TBs spanning the second number of time slots, wherein the indication is included in a DCI or in a time domain resource allocation (TDRA) table.

16. The UE of claim 11, wherein the second number of time slots comprises a first time slot and a second time slot, wherein the first time slot comprises a plurality of rate matching output bits for the PDSCH transmission, and the second time slot comprises the same number of rate matching output bits for the PDSCH transmission. 17 . The UE of claim 11 , wherein the configuration for the PDSCH transmission of the TBs across the first number of time slots further comprises an indication to repeat the PDSCH transmission of the TBs across the first number of time slots for a second time.

18. The UE of claim 11, wherein allocating the second number of time slots used by the UE to support the PDSCH transmission comprises allocating the second number of time slots based on available time slots for the UE.

19. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform operations comprising: receiving, via a downlink from a base station, a configuration for a physical downlink shared channel (PDSCH) transmission for transport blocks (TBs) spanning a first number of time slots, wherein the configuration includes an indication of the first number of time slots; Determining a transport block size (TBS) for the PDSCH transmission; allocating a second number of time slots used by the UE to support the PDSCH transmission; receiving the PDSCH transmission of the TBs spanning the second number of time slots based on the TBS for the PDSCH transmission satisfying a condition; decoding the received PDSCH transmission across the second number of time slots to obtain the TBs; and Feedback is transmitted to the base station based on the decoded PDSCH transmission.

20. The non-transitory computer readable medium of claim 19, wherein the configuration comprises a time domain resource allocation (TDRA) table having an indication of the first number of time slots used for the PDSCH transmission.

Images