Physical downlink shared channel resource for reduced-capability user equipment
By optimizing resource allocation schemes based on UE capability messages, the problem of insufficient data transmission efficiency for bandwidth-constrained and low-complexity UEs in the existing system is solved, and efficient communication support for these UEs is achieved.
Patent Information
- Application Number
- CN202080065740.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-09-24
- Filing Date
- 2020-09-25
- Publication Date
- 2025-10-21
- Estimated Expiration
- 2040-09-25
AI Technical Summary
Existing wireless communication systems struggle to effectively support data transmission for user equipment (UE) types with reduced antenna counts, bandwidth, low complexity, and low transmit power, resulting in deficiencies in resource allocation and data transmission efficiency for these UEs.
Through the UE capability message mechanism, the base station selects a resource allocation scheme based on the UE type indication, including techniques such as distribution on subband subsets of the bandwidth portion, use of low coding rate, intra-slot repetition, and inter-BWP frequency hopping, to optimize resource allocation to support the data transmission of these UEs.
It improves the efficiency and reliability of data transmission for UE types with reduced resources, and ensures effective communication support for bandwidth-constrained, low-complexity devices.
Smart Images

Figure CN114424658B_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to the following applications: U.S. patent application No. 17 / 031,869, entitled “PHYSICAL DOWNLINK SHARED CHANNEL RESOURCES FOR REDUCED CAPABILITY USEREQUIPMENT,” filed by LIU et al. on September 24, 2020; and U.S. provisional patent application No. 62 / 907,499, entitled “PHYSICAL DOWNLINK SHARED CHANNEL RESOURCES FOR REDUCED CAPABILITY USEREQUIPMENT,” filed by LIU et al. on September 27, 2019, each of which is assigned to the assignee of this application. Technical Field
[0003] The following relates generally to wireless communications, and more particularly to physical downlink shared channel (PDSCH) resources for reduced capability user equipment (UE). Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A professional systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication for multiple communication devices (which may also be referred to as UEs). Summary of the Invention
[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting physical downlink shared channel (PDSCH) resources for user equipment (UE) with reduced capabilities. In summary, the described techniques provide various mechanisms to ensure appropriate scheduling for UE types with reduced number of antennas, reduced bandwidth, and the like. For example, a UE type may be associated with limited bandwidth, low complexity, low transmit power level, a smaller number of receive antennas, extended battery life, and the like. A UE may send or otherwise provide a UE capabilities message that carries or otherwise conveys an indication of the UE type. The UE capabilities message may typically be sent to a base station, but it will be appreciated that in some cases (e.g., when the UE is operating in idle mode), the UE capabilities message may be provided to a network entity. Based on the UE type indicated in the UE capabilities message, both the base station and the UE are aware that the UE type is associated with, for example, reduced bandwidth, reduced number of antennas, low complexity, or low transmit power level. The base station (or the network entity when the UE is operating in idle mode) may select a resource allocation scheme for downlink grants for the UE based on the UE capabilities message (e.g., based on the UE type). The base station may send a downlink grant to the UE based on the resource allocation scheme, the downlink grant identifying or otherwise indicating downlink resources to be used for downlink transmission. The base station may send data transmissions to the UE based on the downlink grant. Although various variations of the resource allocation scheme are described in detail below, some aspects may include interleaving / discontinuous resource blocks (RBs) distributed across a subset of subbands of a bandwidth part (BWP), using a lower coding rate for wideband data transmission, using intra-slot repetition for wideband short data channel transmission, using inter-BWP and inter-slot hopping for narrowband long data transmission, etc. Thus, aspects of the described technology provide various enhancements to data transmissions (e.g., PDSCH transmissions) supporting reduced capability UE types.
[0006] A method for wireless communication at a UE is described. The method may include: sending a UE capabilities message to a base station, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capabilities message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion of the UE; monitoring a wireless channel based on the downlink grant; and receiving the data transmission based on the monitoring of the wireless channel.
[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a UE capability message to a base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; based on the UE capability message, receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme associated with the UE type and a supported bandwidth portion of the UE; monitor a wireless channel based on the downlink grant; and receive the data transmission based on the monitoring of the wireless channel.
[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include means for: sending a UE capabilities message to a base station, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capabilities message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion of the UE; monitoring a wireless channel based on the downlink grant; and receiving the data transmission based on the monitoring of the wireless channel.
[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: send a UE capabilities message to a base station, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; based on the UE capabilities message, receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme associated with the UE type and a supported bandwidth portion of the UE; monitor a wireless channel based on the downlink grant; and receive the data transmission based on the monitoring of the wireless channel.
[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the data transmission may include operations, features, units, or instructions for receiving the data transmission in interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported BWP, the subset being based on the UE type.
[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the data transmission may include operations, features, means, or instructions for receiving the data transmission over the supported BWP and using a low coding rate, the low coding rate being based on the UE type.
[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying a scaling factor for the data transmission using the low coding rate based on a scaling factor of a transmit block size, the scaling factor being based on the UE type.
[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, a first demodulation reference signal (DMRS) transmission may be sent during a first time period in a first portion of a time slot, and a second DMRS transmission may be sent during a second time period in a second portion of the time slot, the first time period of the first portion of the time slot being different from the second time period of the second portion of the time slot.
[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the data transmission may include operations, features, means, or instructions for receiving a first transmission of the data transmission and a repeated transmission of the data transmission in a time slot.
[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: identifying a DMRS configuration for receiving the first transmission and the repeated transmission in the time slot; and receiving the data transmission based on the DMRS configuration.
[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration may include operations, features, units, or instructions for performing the following operations: receiving a first DMRS transmission during a first portion of the time slot for the first transmission and receiving a second DMRS transmission during a second portion of the time slot for the repeated transmission.
[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first DMRS transmission may be received during an initial time period of the first portion of the time slot, and the second DMRS transmission may be received during the initial time period of the second portion of the time slot.
[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first DMRS transmission may be received during a first time period of the first portion of the time slot for the first transmission, and the second DMRS transmission may be received during a second time period of the second portion of the time slot for the repeated transmission, the first time period of the first portion of the time slot being different from the second time period of the second portion of the time slot.
[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first transmission and the repeated transmission occur during the same symbol configuration or different symbol configurations in the time slot.
[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying a first starting symbol for the first transmission and a second starting symbol for the repeated transmission based on a downlink aggregation factor for data repetition within a time slot.
[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on the time slot in which the first transmission and the repeated transmission can be received, sending a feedback signal for the data transmission during a subsequent time slot having a time gap for processing.
[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving one or more additional repetitions of the data transmission in a second time slot that occurs after the time slot in which the first transmission and the repetition may be received; and sending a feedback signal during a subsequent time slot having a time gap for processing based on the second time slot in which the one or more repetitions may be received.
[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the data transmission may include operations, features, units, or instructions for receiving a first portion of the data transmission in a first time slot and on the first subband supporting BWP; and receiving a second portion of the data transmission in a second time slot on the second subband supporting BWP, wherein the first subband may be a different subband from the second subband.
[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving the first portion of the data transmission and the second portion of the data transmission according to the same time domain configuration or different time domain configurations between the first time slot and the second time slot.
[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first subband and the second subband may be in the same BWP or in different BWPs.
[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining that the first subband may be in a first BWP and the second subband may be in a second BWP that may be different from the first BWP; and performing a retuning operation during a retuning gap between receiving the first portion and receiving the second portion.
[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the retuning gap can be a last portion of the first subband in a first BWP, or a first portion of the second subband in a second BWP, or a combination thereof.
[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving the first portion in the first time slot and the second portion in the second time slot based on redundancy versions (RVs) associated with the first portion and the second portion of the data transmission.
[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving the data transmission based on a slot index, a repetition index, or a combination thereof.
[0030] A method of wireless communication at a base station is described. The method may include receiving a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; selecting a resource allocation scheme for a downlink grant for the UE based on the UE capability message and a supported bandwidth portion of the UE; sending a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme; and sending the data transmission to the UE based on the downlink grant.
[0031] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; select a resource allocation scheme for a downlink grant for the UE based on the UE capability message and a supported bandwidth portion of the UE; send a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme; and send the data transmission to the UE based on the downlink grant.
[0032] Another apparatus for wireless communication at a base station is described. The apparatus may include means for: receiving a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; selecting a resource allocation scheme for a downlink grant for the UE based on the UE capability message and a supported bandwidth portion of the UE; sending a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme; and sending the data transmission to the UE based on the downlink grant.
[0033] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: receive a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; select a resource allocation scheme for a downlink grant for the UE based on the UE capability message and a supported bandwidth portion of the UE; send a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme; and send the data transmission to the UE based on the downlink grant.
[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the data transmission may include operations, features, units, or instructions for sending the data transmission in interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported BWP, the subset being based on the UE type.
[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the data transmission may include operations, features, means, or instructions for sending the data transmission over the supported BWP and using a low coding rate, the low coding rate being based on the UE type.
[0036] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying, based on a scaling factor of a transmit block size, the scaling factor to be used for the data transmission using the low coding rate, the scaling factor being based on the UE type.
[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the data transmission may include operations, features, means, or instructions for sending a first transmission of the data transmission and repeated transmissions of the data transmission in a time slot.
[0038] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: identifying a DMRS configuration for sending the first transmission and the repeated transmission in the time slot; and sending the data transmission based on the DMRS configuration.
[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DMRS configuration may include operations, features, units, or instructions for performing the following operations: sending a first DMRS transmission during a first portion of the time slot for the first transmission and sending a second DMRS transmission during a second portion of the time slot for the repeated transmission.
[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first DMRS transmission may be sent during an initial time period of the first portion of the time slot for the first transmission, and the second DMRS transmission may be sent during the initial time period of the second portion of the time slot for the repeated transmission.
[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first transmission and the repeated transmission occur during the same symbol configuration or different symbol configurations in the time slot.
[0042] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for identifying a first starting symbol for the first transmission and a second starting symbol for the repeated transmission based on a downlink aggregation factor for data repetition within a time slot.
[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: based on the time slot in which the first transmission and the repeated transmission can be sent, receiving a feedback signal for the data transmission during a subsequent time slot having a time gap for processing.
[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending one or more additional repetitions of the data transmission in a second time slot that occurs after the time slot in which the first transmission and the repetition may be sent; and receiving a feedback signal during a subsequent time slot having a time gap for processing based on the second time slot in which the one or more repetitions may be sent.
[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the data transmission may include operations, features, units, or instructions for sending a first portion of the data transmission in a first time slot and on the first subband supporting BWP; and sending a second portion of the data transmission in a second time slot on the second subband supporting BWP, wherein the first subband may be a different subband from the second subband.
[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending the first portion of the data transmission and the second portion of the data transmission according to the same time domain configuration or different time domain configurations between the first time slot and the second time slot.
[0047] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first subband and the second subband may be in the same BWP or in different BWPs.
[0048] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for determining that the first subband may be in a first BWP and the second subband may be in a second BWP that may be different from the first BWP; and configuring a retuning gap between transmitting the first portion and receiving the second portion.
[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the retuning gap includes a last portion of the first subband in a first BWP, or a first portion of the second subband in a second BWP, or a combination thereof.
[0050] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending the first portion in the first time slot and the second portion in the second time slot based on RVs associated with the first portion and the second portion of the data transmission.
[0051] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending the data transmission based on a slot index, a repetition index, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS
[0052] Figure 1
[0014] An example of a system for wireless communications supporting physical downlink shared channel (PDSCH) resources for reduced capability user equipment (UE) in accordance with aspects of the present disclosure is shown.
[0053] Figure 2 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0054] Figure 3 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0055] Figure 4 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0056] Figure 5 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0057] Figure 6An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0058] Figure 7 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0059] Figure 8 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0060] Figure 9 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0061] Figure 10 An example set of slot configurations supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure is shown.
[0062] Figure 11 and 12 A block diagram of an apparatus supporting PDSCH resources for reduced capability UEs is shown in accordance with aspects of the present disclosure.
[0063] Figure 13 A block diagram of a communications manager supporting PDSCH resources for reduced capability UEs is shown in accordance with aspects of the present disclosure.
[0064] Figure 14 A diagram is shown of a system including devices supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure.
[0065] Figure 15 and 16 A block diagram of an apparatus supporting PDSCH resources for reduced capability UEs is shown in accordance with aspects of the present disclosure.
[0066] Figure 17 A block diagram of a communications manager supporting PDSCH resources for reduced capability UEs is shown in accordance with aspects of the present disclosure.
[0067] Figure 18 A diagram is shown of a system including devices supporting PDSCH resources for reduced capability UEs in accordance with aspects of the present disclosure.
[0068] Figures 19 to 22 A flow chart illustrating a method of supporting PDSCH resources for reduced capability UEs according to aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0069] Some wireless communication systems use frequency and / or time domain diversity to support improved system performance and throughput. For example, such wireless communication systems can utilize various techniques, alone or in combination, to improve system capacity and performance. Such techniques include, but are not limited to, discontinuous resource blocks (RBs) within a wide bandwidth part (BWP), distributed resource allocation within a wide BWP, multi-slot aggregation for the physical downlink shared channel (PDSCH), and the like. These wireless communication systems generally do not support frequency hopping. However, technological advances have also resulted in certain user equipment (UE) types being unable to utilize some or all of these advanced techniques. For example, some UE types are associated with limited or reduced bandwidth, low complexity levels, low maximum transmit power levels, reduced number of antennas, or extended battery life. Such UE types may include wearable devices, Internet of Things (IoT) devices, and Machine Type Communication (MTC) devices.
[0070] Various aspects of the present disclosure are first described in the context of a wireless communication system. In summary, the described techniques provide various mechanisms to ensure appropriate scheduling for UE types with reduced number of antennas, reduced bandwidth, etc. For example, the UE type may be associated with, for example, limited bandwidth, low complexity, low transmit power level, fewer number of receive antennas, extended battery life, etc. The UE may send or otherwise provide a UE capability message that carries or otherwise conveys an indication of the UE type. The UE capability message may typically be sent to a base station, but it will be appreciated that in some cases (e.g., when the UE is operating in idle mode), the UE capability message may be provided to a network entity.
[0071] The UE capability message may be a radio resource control (RRC) layer message sent by the UE to a base station or other network entity, for example, during an initial registration procedure. The UE capability message may use a set of defined or standardized information elements or other fields to detail the capabilities or attributes of the UE and the features supported by the UE.
[0072] Based on the UE type indicated in the UE capability message, both the base station and the UE know that the UE type is associated with, for example, reduced bandwidth, reduced number of antennas, low complexity, or low transmit power level. The base station (or a network entity when the UE is operating in idle mode) can select a resource allocation scheme for a downlink grant for the UE based on the UE capability message (e.g., based on the UE type). The base station can send a downlink grant to the UE based on the resource allocation scheme, which identifies or otherwise indicates the downlink resources to be used for downlink transmission. The base station can send a data transmission to the UE based on the downlink grant. Although multiple variations of resource allocation schemes are described below, some aspects may include interleaving / discontinuous RBs distributed across subband subsets of a BWP, using a low coding rate for wideband data channel transmissions, using intra-slot repetition for wideband short data channel transmissions, using inter-BWP and inter-slot hopping for narrowband long data channel transmissions, and the like. Thus, various aspects of the described techniques provide various enhancements to supporting data transmissions (e.g., PDSCH) of different UE types.
[0073] Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to PDSCH resources for reduced capability UEs.
[0074] Figure 1 An example of a wireless communication system 100 that supports PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure is shown. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 can be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A professional network, or a new radio (NR) network. In some cases, the wireless communication system 100 can support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices.
[0075] The base station 105 can communicate wirelessly with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a wireless base station, an access point, a wireless transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a giganode B (any of which may be referred to as a gNodeB or gNB), a Home Node B, a Home evolved Node B, or some other appropriate terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein is capable of communicating with various types of base stations 105 and network devices (including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.).
[0076] Each base station 105 may be associated with a particular geographic coverage area 110 in which it supports communications with various UEs 115. Each base station 105 may provide communication coverage for the respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105 or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, while uplink transmissions may also be referred to as reverse link transmissions.
[0077] The geographic coverage area 110 for a base station 105 can be divided into sectors that constitute a portion of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for a macrocell, a small cell, a hotspot, or other types of cells, or various combinations thereof. In some examples, the base stations 105 can be mobile and, therefore, provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and the overlapping geographic coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network, in which different types of base stations 105 provide coverage for various geographic coverage areas 110.
[0078] The term "cell" refers to a logical communication entity used for communication with base station 105 (e.g., on a carrier), and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, a carrier can support multiple cells, and different cells can be configured according to different protocol types (e.g., MTC, narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that can provide access to different types of devices. In some cases, the term "cell" can refer to a portion of the geographic coverage area 110 (e.g., a sector) on which the logical entity operates.
[0079] UE 115 can be dispersed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a mobile device, wireless device, remote device, handheld device, or user equipment, or some other appropriate terminology, where "device" can also be referred to as a unit, station, terminal, or client. UE 115 can also be a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 can also refer to a wireless local loop (WLL) station, an IoT device, an Internet of Everything (IoE) device, or an MTC device, which can be implemented in various items such as appliances, vehicles, meters, and the like.
[0080] Some UEs 115 (e.g., MTC or IoT devices) may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that incorporate sensors or meters to measure or capture information and relay that information to a central server or application, which may utilize the information or present it to a human interacting with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing for services.
[0081] Some UEs 115 may be configured to employ a mode of operation that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power conservation techniques for the UE 115 include entering a power-saving "deep sleep" mode when not engaged in active communications or operating over a limited bandwidth (e.g., in accordance with narrowband communications). In some cases, the UE 115 may be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communications for these functions.
[0082] In some cases, UE 115 can also communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol). One or more UEs 115 in a group of UEs 115 utilizing D2D communication can be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group can be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, multiple groups of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some cases, the base station 105 facilitates the scheduling of resources for the D2D communication. In other cases, the D2D communication is performed between the UEs 115 without involving the base station 105.
[0083] The base stations 105 can communicate with the core network 130 and with each other. For example, the base stations 105 can interface with the core network 130 via a backhaul link 132 (e.g., via an S1, N2, N3, or other interface). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) over a backhaul link 134 (e.g., via an X2, Xn, or other interface).
[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be transported through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to network operator IP services. Operator IP services may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet switched (PS) streaming services.
[0085] At least some of the network devices (e.g., base station 105) may include subcomponents such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity may communicate with UE 115 through multiple other access network transport entities (which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs)). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., base station 105).
[0086] The wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features. However, the waves can penetrate structures sufficiently for a macro cell to provide service to a UE 115 located indoors. Transmission using UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to transmission using the lower frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.
[0087] The wireless communication system 100 may also operate in the Super High Frequency (SHF) region, which uses a frequency band from 3 GHz to 30 GHz (also known as the centimeter band). The SHF region includes frequency bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band, which may be opportunistically used by devices that can tolerate interference from other users.
[0088] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 can support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices can be even smaller and more closely spaced than the UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions can vary depending on the country or regulatory agency.
[0089] In some cases, the wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed radio frequency spectrum band (e.g., the 5 GHz ISM band). When operating in an unlicensed radio frequency spectrum band, wireless devices (e.g., base stations 105 and UEs 115) can employ a listen-before-talk (LBT) process to ensure that the frequency channel is idle before sending data. In some cases, operations in an unlicensed band can be based on a carrier aggregation configuration in combination with component carriers operating in a licensed band (e.g., LAA). Operations in an unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplexing in an unlicensed spectrum can be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of both.
[0090] In some examples, the base station 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may employ a transmission scheme between a transmitting device (e.g., the base station 105) and a receiving device (e.g., the UE 115), wherein the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (which may be referred to as spatial multiplexing). For example, the transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Similarly, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.
[0091] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to form or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array so that signals propagating in a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying certain amplitude and phase offsets to the signals carried by each of the antenna elements associated with the device. The adjustments associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).
[0092] In one example, the base station 105 can use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, the base station 105 can transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, and the some signals may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. The transmissions in different beam directions can be used (e.g., by the base station 105 or a receiving device (e.g., UE 115)) to identify the beam direction for subsequent transmission and / or reception by the base station 105.
[0093] Base station 105 may transmit some signals (e.g., data signals associated with a particular receiving device) in a single beam direction (e.g., a direction associated with a receiving device (e.g., UE 115)). In some examples, the beam direction associated with transmissions along the single beam direction may be determined at least in part based on signals transmitted in different beam directions. For example, UE 115 may receive one or more of the signals transmitted by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal received that has the highest signal quality or otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).
[0094] When receiving various signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (e.g., UE 115, which may be an example of a mmW receiving device) may try multiple receive beams. For example, the receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (any of the above operations may be referred to as "listening" according to different receive beams or receive directions). In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). A single receive beam can be aligned in a beam direction determined at least in part based on listening according to different receive beam directions (e.g., a beam direction determined at least in part to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening according to multiple beam directions).
[0095] In some cases, the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with a base station 105 may be located at different geographical locations. A base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with a UE 115. Similarly, a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
[0096] In some cases, the wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate on the logical channel. The medium access control (MAC) layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration and maintenance of the RRC connection (which supports radio bearers for user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, the transport channel can be mapped to the physical channel.
[0097] In some cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood that data is correctly received on the communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise conditions). In some cases, a wireless device may support same-slot HARQ feedback, wherein the device may provide HARQ feedback in a particular time slot for data received in previous symbols in that time slot. In other cases, the device may provide HARQ feedback in subsequent time slots or according to some other time interval.
[0098] The basic time unit (which may be referred to as T s =1 / 30,720,000 seconds). The time intervals of communication resources can be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period can be denoted as T f =307,200T s. A radio frame can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame can include 10 subframes numbered from 0 to 9, and each subframe can have a duration of 1 ms. The subframe can also be divided into 2 time slots, each time slot has a duration of 0.5 ms, and each time slot can contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added in front of each symbol period). Excluding the cyclic prefix, each symbol period can contain 2048 sampling periods. In some cases, a subframe can be the minimum scheduling unit of the wireless communication system 100 and can be referred to as a transmission time interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 can be shorter than a subframe or can be dynamically selected (e.g., in a burst of a shortened TTI (sTTI) or in a component carrier selected to use sTTI).
[0099] In some wireless communication systems, a time slot can be further divided into multiple mini-slots containing one or more symbols. In some instances, a symbol of a mini-slot or a mini-slot can be the smallest scheduling unit. The duration of each symbol can vary depending on, for example, the subcarrier spacing or the frequency band of operation. In addition, some wireless communication systems can implement time slot aggregation, in which multiple time slots or mini-slots are aggregated and used for communication between UE 115 and base station 105.
[0100] The term "carrier" refers to a collection of radio frequency spectrum resources having a defined physical layer structure for supporting communications on the communication link 125. For example, a carrier of the communication link 125 may include a portion of a radio frequency spectrum band that operates according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. A carrier may be associated with a predefined frequency channel (e.g., an Evolved Universal Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be placed according to a channel grid for discovery by the UE 115. A carrier may be downlink or uplink (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).
[0101] The organizational structure of a carrier can be different for different radio access technologies (e.g., LTE, LTE-A, LTE-A Professional, NR). For example, communications on a carrier can be organized based on TTIs or time slots, each of which can include user data and control information or signaling to support decoding of the user data. A carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling to coordinate operations for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier can also have acquisition signaling or control signaling to coordinate operations for other carriers.
[0102] Physical channels may be multiplexed on a carrier according to various techniques. For example, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using time division multiplexing (TDM), frequency division multiplexing (FDM), or a hybrid TDM-FDM technique. In some examples, the control information sent in the physical control channel may be distributed in a concatenated manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).
[0103] A carrier can be associated with a particular bandwidth of radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth can be one of a plurality of predetermined bandwidths of the carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or RBs) within a carrier (e.g., an "in-band" deployment of a narrowband protocol type).
[0104] In a system employing MCM technology, a resource element may consist of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements a UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for the UE 115 may be. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with the UE 115.
[0105] A device of the wireless communication system 100 (e.g., a base station 105 or a UE 115) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and / or a UE 115 that supports simultaneous communication via carriers associated with more than one different carrier bandwidths.
[0106] The wireless communication system 100 may support communication with the UE 115 on multiple cells or carriers (a feature that may be referred to as carrier aggregation or multi-carrier operation). Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both FDD component carriers and TDD component carriers.
[0107] In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may be characterized by one or more characteristics including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be used by UEs 115 that are unable to monitor the entire carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to save power).
[0108] In some cases, an eCC may utilize a different symbol duration than other component carriers, which may include using a reduced symbol duration compared to the symbol duration of other component carriers. The shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. A device utilizing an eCC (e.g., a UE 115 or a base station 105) may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, or 80 MHz) with a reduced symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.
[0109] In addition, the wireless communication system 100 can be an NR system that can utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility of eCC symbol duration and subcarrier spacing can allow eCC to be used across multiple spectrums. In some examples, NR shared spectrum can improve spectrum utilization and spectrum efficiency, especially through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.
[0110] UE 115 may send a UE capabilities message to base station 105, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for UE 115. UE 115 may receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme based at least in part on the UE capabilities message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion for UE 115. UE 115 may monitor a radio channel based at least in part on the downlink grant. UE 115 may receive the data transmission based at least in part on the monitoring of the radio channel.
[0111] Base station 105 may receive a UE capabilities message from UE 115, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for UE 115. Base station 105 may select a resource allocation scheme for a downlink grant for UE 115 based at least in part on the UE capabilities message and the supported bandwidth portion of the UE. Base station 105 may send a downlink grant to the UE for downlink resources for data transmission based on the resource allocation scheme. Base station 105 may send a data transmission to UE 115 based at least in part on the downlink grant.
[0112] Although these techniques are described as being performed by base station 105, it should be understood that references to base station 105 performing features in the context of the described techniques may actually be implemented by base station 105 and / or a network entity (such as an MME). In one example, this may include base station 105 (e.g., a gNB) performing the described techniques when UE 115 operates in RRC connected mode, and a network entity (e.g., an MME) performing the described techniques when UE 115 operates in RRC idle or inactive mode. In another example, UE 115 may report the capability to a network entity (e.g., the MME via NAS signaling). Base station 105 then performs the UE's features based on the relevant information obtained from the network entity.
[0113] Figure 2An example time slot configuration set 200 is shown for supporting PDSCH resources for UEs with reduced capabilities in accordance with various aspects of the present disclosure. In some examples, the example time slot configuration set 200 can implement various aspects of the wireless communication system 100. Various aspects of the example time slot configuration set 200 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, various aspects of the example time slot configuration set 200 can be implemented by a base station when the UE is operating in RRC connected mode, and / or various aspects of the example time slot configuration set 200 can be implemented in a network entity (e.g., an MME) when the UE is operating in RRC inactive or RRC idle mode. Broadly speaking, the example time slot configuration set 200 shows four examples of time slot configurations for supporting PDSCH enhancements for UE types with reduced capabilities (or associated with reduced capabilities).
[0114] Some wireless communication systems can utilize various diversity techniques to improve system throughput and performance. Diversity techniques can be used in the frequency domain, spatial domain, and / or time domain. In the frequency domain, this can include configuring discontinuous RBs within a wide BWP and using distributed resource allocation within the wide BWP to achieve frequency diversity over a wide bandwidth. In the time domain, this can include using multi-slot aggregation for PDSCH. Multi-slot repetition can be on the same symbol allocation with an aggregation factor (e.g., pdsch-AggregationFactor {2, 4, or 8}) distributed across consecutive slots, for example, for combining. However, such techniques may be problematic for certain UEs with reduced capabilities (e.g., certain UE types). For example, some techniques may require wider bandwidth or longer transmission time, which is detrimental to power saving for certain UE types. Although some UE types support such techniques, other UE types may not support (or at least may not fully support) such techniques.
[0115] For example, some UE types may be associated with reduced or limited bandwidth (e.g., 5 MHz / 10 MHz / 20 MHz, which may be greater than the SSB bandwidth), low complexity (e.g., reduced processing power / requirements, less memory, or fewer transmit / receive chains), lower maximum transmit power levels (e.g., 20 dBm or 14 dBm), reduced number of antennas (e.g., one or two receive antennas), increased power savings / long battery life (e.g., measured in years), reduced or no mobility, transmitting small amounts of data, etc. However, such reduced-capability UEs (e.g., UEs with reduced bandwidth or a reduced number of antennas) must still coexist with eMBB, URLLC, or LTE-NB IoT / MTC devices. Therefore, references to UE types herein generally refer to these reduced-capability UEs.
[0116] Thus, aspects of the described technology provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UEs). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station) that carries or otherwise conveys an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life, or small data transmission. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC control elements (CEs), etc.), or during registration (e.g., using NAS signals to a network entity), or thereafter.
[0117] A base station (or network entity) may generally select a resource allocation scheme for a UE, which may be used to send downlink grants and / or data transmissions to the UE based on the UE type. Example slot configuration set 200 illustrates four non-limiting examples of slot configurations that may be components of a resource allocation scheme selected for a UE according to aspects of the described techniques.
[0118] In a first example, the resource allocation scheme may correspond to a slot configuration 205. Slot configuration 205 illustrates an example of distributed resource allocation with interleaved / non-contiguous RBs distributed across a subset of available subbands in a supported BWP. Slot configuration 205 may include a PDCCH 225 (e.g., a downlink grant for downlink resources) distributed across the entire BWP. PDCCH 225 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 205). PDCCH 225 may span the first symbol of a slot. During the first symbol following PDCCH 225, the base station may transmit a data transmission by transmitting DMRS 235 followed by PDSCH 230. Broadly speaking, the data transmission may correspond to PDSCH 230, and channel estimation for the data transmission may be based on DMRS 235. However, data transmission may be transmitted using only a subset of the available subbands in the entire BWP (e.g., a reduced bandwidth supported by the UE type).
[0119] In a second example, the resource allocation scheme may correspond to a slot configuration 210. Slot configuration 210 illustrates an example of data transmission distributed across a supported BWP and using a low coding rate, where the low coding rate is based on the UE type. Slot configuration 210 may include a PDCCH 225 (e.g., a downlink grant for downlink resources) distributed across the BWP. The PDCCH 225 may carry or otherwise convey an indication of downlink resources based on the resource allocation scheme (e.g., based on slot configuration 210). The PDCCH 225 may span the first symbol of a slot. During the first symbol following the PDCCH 225, the base station may transmit a data transmission by transmitting a DMRS 235 followed by a PDSCH 230. Broadly speaking, the data transmission may correspond to the PDSCH 230, and the channel estimation for the data transmission may be based on the DMRS 235. The data transmission may be transmitted using all available subbands in the supported BWP (e.g., the reduced bandwidth supported by the UE type).
[0120] In a third example, a resource allocation scheme may correspond to a slot configuration 215. Slot configuration 215 illustrates an example of data transmission distributed across a supporting BWP and using repetitions of data transmission within a slot, where the repetition rate is based on the UE type. Slot configuration 215 may include a PDCCH 225 (e.g., a downlink grant for downlink resources) distributed across the BWP. PDCCH 225 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 215). PDCCH 225 may span the first symbol of a slot. During the first symbol following PDCCH 225, the base station may transmit a data transmission by transmitting DMRS 235 during the slot, followed by a first transmission of PDSCH 230 and one or more repetitions of PDSCH 230 (two repetitions are shown by way of example). Broadly speaking, the data transmission may correspond to PDSCH 230, and channel estimation for the data transmission may be based on DMRS 235. All available subbands in a supported BWP (e.g., a reduced bandwidth supported by the UE type) may be used to transmit data transmissions. Thus, slot configuration 215 illustrates an example resource allocation using a wideband short PDSCH 230 (e.g., a subslot-based PDSCH with approximately 1-3 symbols in a slot) with intra-slot repetitions. PDSCH 230 repetitions may share a DMRS 235 (as shown in slot configuration 215) or may have associated intra-slot DMRS for multiple PDSCH repetitions.
[0121] In a fourth example, the resource allocation scheme may correspond to a slot configuration 220. Slot configuration 220 illustrates an example of data transmissions distributed across a narrowband long PDSCH 230 between / within a BWP using inter-slot hopping, based on UE type. More specifically, slot configuration 220 illustrates an example in which a first portion of a data transmission is transmitted in a first slot on a first subband supporting a BWP, and a second portion of the data transmission is transmitted in a second slot on a second subband supporting a BWP, where the first and second subbands are different. In the first slot, slot configuration 220 may include a PDCCH 225 (e.g., a downlink grant for downlink resources) distributed across the BWP. The PDCCH 225 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 220). The PDCCH 225 may span the first symbol of the slot. During the first symbol after the PDCCH 225 and on the first subband, the base station may transmit a data transmission by transmitting a DMRS 235 followed by a first transmission of the PDSCH 230 in the first subband (e.g., the first portion of the data transmission). In the second time slot, the time slot configuration 220 may include PDCCHs 225 (e.g., downlink grants for downlink resources) distributed across the BWP. In some examples, the PDCCH 225 in the second time slot may be optional (e.g., the PDCCH 225 in the first time slot may schedule a data transmission for the second time slot). During the first symbol after the PDCCH 225 and on the second subband, the base station may transmit a data transmission by transmitting a DMRS 235 followed by a second transmission of the PDSCH 230 in the second subband (e.g., the second portion of the data transmission). Broadly speaking, the data transmission may correspond to the PDSCH 230 and DMRS 235 in the first and second time slots. The data transmission may be transmitted using a subset of the available subbands in the supported BWP (e.g., a reduced bandwidth supported by the UE type). Thus, the slot configuration 220 illustrates an exemplary resource allocation scheme using a narrowband / long PDSCH 230 (eg, a slot-based PDSCH) with inter / intra-BWP and inter-slot frequency hopping.
[0122] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 205, 210, 215, and / or 220.
[0123] In some aspects, a PDSCH scrambling sequence may be used. The initialization seed for the scrambling sequence for NR PDSCH may be defined as c init =n RNTI *215 +q*2 14 +n ID , where q is the codeword index, n ID is the cell ID or sequence ID, and n RNTI is the RNTI associated with the PDSCH. For UE types with reduced capabilities (e.g., NR light UEs), PDSCH repetition using the same scrambling sequence may not be conducive to interference randomization. Therefore, aspects of the described technology may introduce a time-varying initialization seed for the scrambling sequence for UE types with reduced capabilities. The PDSCH repetition / hopping may be defined as c init =n RNTI *2 15 +q*2 14 +n s *2 10 +n ID , where n s is the slot index within the radio frame with the value {0, ..., 9}. Alternatively, n s The repetition index may refer to a PDSCH repetition with a value of {0, ..., 15}.
[0124] Figure 3 An example time slot configuration set 300 is shown for supporting PDSCH resources for UEs with reduced capabilities according to various aspects of the present disclosure. In some examples, the example time slot configuration set 300 can implement aspects of the wireless communication system 100 and / or the example time slot configuration set 200. Various aspects of the example time slot configuration set 300 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, various aspects of the example time slot configuration set 300 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, various aspects of the example time slot configuration set 300 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the example time slot configuration set 300 shows four examples of time slot configurations for supporting PDSCH enhancements for UE types with reduced capabilities.
[0125] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not support all of these techniques. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0126] For example, some reduced capability UE types may be associated with small downlink packet transmissions (e.g., NR light UEs). This may include a transport block size (TBS) between 16-100 (e.g., in NR, the minimum TBS is 24, and in LTE NBIoT, the minimum TBS is 16). Such techniques may include using the lowest MCS (e.g., MCS0) with a modulation order (M) of two for QPSK, a code rate (R) of 30 / 1024, and formula N info =8*floor(M*R*N RB *12*N symbol ) / 8, where N symbol =ceiling(N info / (M*R*N RB *12)). However, aspects of the described technology may introduce a TB scaling factor for data transmission with lower TB. The scaling factor may be indicated in DCI (e.g., downlink grant), RRC signaling, etc. The scaling factor may be applied according to the following table:
[0127]
[0128] Therefore, the scaling factor can be set to a value of 1, 0.5, 0.25, or 0.125, and N info =8*floor(M*R*N RB *12*N symbol ) / 8 to N info =8*floor(S*M*R*N RB *12*N symbol ) / 8. Then, when the scaling factor is applied, the equivalent coding rate can be S*R. Thus, aspects of the described techniques can identify a scaling factor for data transmission using a low coding rate based at least in part on a scaling factor for a TBS, which is based at least in part on a UE type.
[0129] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station) that carries or otherwise conveys an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.) or during registration (e.g., using NAS signaling to a network entity) or thereafter.
[0130] A base station (or network entity) can generally select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. The example slot configuration set 300 shows four non-limiting examples of slot configurations that can be components of such a resource allocation scheme according to various aspects of the described technology. In particular, the example slot configuration set 300 shows two examples where TBS=16 (e.g., a lower TBS supported by traditional LTE NB IoT) and two other examples where TBS=24 (e.g., the lowest TBS supported by traditional NR UEs).
[0131] In a first example, the resource allocation scheme may correspond to a slot configuration 305. Slot configuration 305 illustrates an example in which the scaling factor is set to 1 and the TBS is 16. Slot configuration 305 may include a PDCCH 325 (e.g., a grant for downlink resources) transmitted in the first three symbols of the slot. PDCCH 325 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 305). During the first symbol following PDCCH 325, the base station may transmit a data transmission by transmitting DMRS 335 in one symbol followed by PDSCH 330 in the next symbol. Broadly speaking, the data transmission may correspond to PDSCH 330 and DMRS 335. The data transmission may be transmitted using available subbands within the entire BWP (e.g., a reduced bandwidth supported by the UE type).
[0132] In a second example, the resource allocation scheme may correspond to a slot configuration 310. Slot configuration 310 illustrates an example in which the scaling factor is set to 0.125 and the TBS is 16. Slot configuration 310 may include a PDCCH 325 (e.g., a grant for downlink resources) transmitted in the first three symbols of the slot. The PDCCH 325 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 310). Starting at the first symbol after the PDCCH 325, the base station may transmit a data transmission by transmitting a DMRS 335 followed by a PDSCH 330 in the next eight symbols of the slot. Broadly speaking, the data transmission may correspond to the PDSCH 330 and the DMRS 335. The data transmission may be transmitted using available subbands within the entire BWP (e.g., a reduced bandwidth supported by the UE type).
[0133] In a third example, the resource allocation scheme may correspond to a slot configuration 315. Slot configuration 315 illustrates an example in which the scaling factor is set to 1 and the TBS is 24. Slot configuration 315 may include a PDCCH 325 (e.g., a grant for downlink resources) transmitted in the first three symbols of the slot. PDCCH 325 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 315). During the first symbol following PDCCH 325, the base station may transmit a data transmission by transmitting DMRS 335 (followed by PDSCH 330 in the next two symbols). Broadly speaking, the data transmission may correspond to PDSCH 330 and DMRS 335. The data transmission may be transmitted using available subbands within the entire BWP (e.g., a reduced bandwidth supported by the UE type).
[0134] In a fourth example, the resource allocation scheme may correspond to a slot configuration 320. Slot configuration 320 illustrates an example in which the scaling factor is set to 0.125 and the TBS is 24. Slot configuration 320 may include a PDCCH 325 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. PDCCH 325 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 320). During the first symbol following PDCCH 325, the base station may transmit a data transmission by transmitting DMRS 335 followed by PDSCH 330 in the next 12 symbols. Broadly speaking, the data transmission may correspond to PDSCH 330 and DMRS 335. The data transmission may be transmitted using available subbands within the entire BWP (e.g., a reduced bandwidth supported by the UE type).
[0135] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 305, 310, 315, and / or 320.
[0136] Figure 4 An example time slot configuration set 400 is shown for supporting PDSCH resources for UEs with reduced capabilities according to various aspects of the present disclosure. In some examples, the example time slot configuration set 400 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200 and / or 300. Various aspects of the example time slot configuration set 400 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, various aspects of the time slot configuration 400 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, various aspects of the time slot configuration 400 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the example time slot configuration set 400 shows two examples of time slot configurations for supporting PDSCH enhancement for UE types with reduced capabilities.
[0137] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not support all of these techniques. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0138] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station) that carries or otherwise conveys an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.) or during registration (e.g., using NAS signals to a network entity) or thereafter.
[0139] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support intra-slot PDSCH repetition. In some aspects, this can include using DMRS 425 with the same frequency domain resource allocation between slots, which may not overlap with symbols carrying PDSCH 420. The DMRS 425 type / symbol location can be indicated by RRC signaling, DCI (e.g., downlink grant), etc. Example slot configuration set 400 shows two non-limiting examples of slot configurations that can be components of such resource allocation schemes according to aspects of the described techniques.
[0140] In a first example, the selected resource allocation scheme may correspond to a slot configuration 405. The slot configuration 405 illustrates an example in which a DMRS 425 is per-UE and shared by all repetitions of the PDSCH 420 in the same slot. The slot configuration 405 may include a PDCCH 415 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. The PDCCH 415 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 405). During the first two symbols after the PDCCH 415, the base station may transmit a data transmission by transmitting a DMRS 425 followed by a first transmission of the PDSCH 420 and one or more repetitions of the PDSCH 420 during the slot (two repetitions are shown by way of example only). Broadly speaking, a data transmission may correspond to the PDSCH 420, each repetition of the PDSCH 420, and the DMRS 425. Additional DMRS 425 transmissions may be provided in one or more of the repetitions of the PDSCH 420 (where one DMRS 425 is shown in the second repetition by way of example only). Data transmissions may be sent using all available subbands in a supported BWP (e.g., a reduced bandwidth supported by the UE type).
[0141] Thus, the slot configuration 405 illustrates an example resource allocation in which a frontloaded DMRS 425 is configured and one (or more) additional DMRS 425 may also be configured. For a small number of PDSCH symbols, some wireless communications may not support additional DMRS 425. When a UE is configured with intra-slot repetition, additional DMRS 425 may be configured to improve channel estimation. The total number of PDSCH 420 symbol configurations in intra-slot repetition may be used to reuse the DMRS 425 pattern configuration. DMRS 425 in the same slot may be jointly decoded for channel estimation. Thus, the slot configuration 405 may support identifying DMRS configurations for a first transmission and a repeated transmission in a slot. Additionally or alternatively, aspects of the slot configuration 405 may support a first DMRS 425 transmission during a first portion of a slot (e.g., during a first PDSCH 420 transmission) and a second DMRS transmission during a second portion of the slot (e.g., during a repeated transmission of the PDSCH 420).
[0142] In a second example, the resource allocation scheme may correspond to a slot configuration 410. Slot configuration 410 illustrates an example in which DMRS 425 is per-UE and may not be shared by all repetitions of PDSCH 420 in the same slot. Slot configuration 410 may include a PDCCH 415 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. PDCCH 415 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to slot configuration 405). During the first symbol following PDCCH 415, the base station may transmit a data transmission by transmitting DMRS 425 during the first symbol, followed by a first transmission of PDSCH 420 and one or more retransmissions of PDSCH 420 during the slot (two retransmissions are shown by way of example only). In slot configuration 410, each repetition of PDSCH 420 is preceded by DMRS 425; for example, each transmission / repetition of PDSCH 420 may be configured with its own corresponding DMRS 425 transmission. Broadly speaking, a data transmission may correspond to the PDSCH 420, each repetition of the PDSCH 420, and the DMRS 425. The data transmission may be sent using all available subbands in a supported BWP (eg, a reduced bandwidth supported by the UE type).
[0143] Thus, the slot configuration 410 illustrates an example resource allocation scheme in which a frontloaded DMRS 425 is configured for each PDSCH 420 repetition. In some examples, the same DMRS pattern can be reused for PDSCH 420 repetitions, e.g., a frontloaded DMRS can be configured for each PDSCH 420 repetition. Thus, the slot configuration 410 can support identifying a DMRS configuration for a first transmission and a repetition transmission in a slot. Additionally or alternatively, aspects of the slot configuration 410 can support a first DMRS 425 during a first portion of a slot (e.g., during a first PDSCH 420 transmission) and a second DMRS transmission during a second portion of the slot (e.g., during each repetition transmission of the PDSCH 420).
[0144] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 405 and / or 410.
[0145] Figure 5 An example time slot configuration set 500 is shown for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure. In some examples, the example time slot configuration set 500 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, and / or 400. Aspects of the example time slot configuration set 500 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, aspects of the example time slot configuration set 500 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, aspects of the example time slot configuration set 500 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the example time slot configuration set 500 shows three examples of time slot configurations for supporting PDSCH enhancement for UE types with reduced capabilities.
[0146] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0147] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station) that carries or otherwise conveys an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.) or during registration (e.g., using NAS signals to a network entity) or thereafter.
[0148] A base station (or network entity) may typically select a resource allocation scheme for a UE that may be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques may support intra-slot PDSCH repetitions. In some aspects, this may include repetitions of each PDSCH using the same frequency domain resource allocation in the same link or multiple allocated resources, but possibly with different starting symbol positions. In some examples, the configuration may be signaled via RRC signaling, in a DCI, or the like, or otherwise indicated. Example slot configuration set 500 shows three non-limiting examples of slot configurations that may be components of a selected resource allocation scheme according to various aspects of the described techniques.
[0149] In a first example, the selected resource allocation scheme may correspond to a slot configuration 505. The slot configuration 505 illustrates an example in which an explicit starting symbol offset is indicated relative to each PDSCH repetition within a slot. This may include avoiding symbol overlap with a DMRS symbol. The slot configuration 505 may include a PDCCH 520 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. The PDCCH 520 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 505). During the first two symbols following the PDCCH 520, the base station may transmit a data transmission by transmitting a DMRS 530 followed by a first transmission of a PDSCH 525 and one or more repetitions of the PDSCH 525 during the slot (two repetitions are shown by way of example only). In some examples, one or more of the repetitions of the PDSCH 525 may include another transmission of the DMRS 530 in the first symbol of the repetition. In general, a data transmission may correspond to a PDSCH 525, each repetition of the PDSCH 525, and a DMRS 530. All available subbands within a supported BWP (e.g., a reduced bandwidth supported by the UE type) may be used to transmit the data transmission. Thus, slot configuration 505 illustrates an example resource allocation scheme, indicating a starting symbol offset value relative to each PDSCH 525 repetition within a slot. DMRS 530 may avoid or otherwise not overlap with symbols used to transmit the PDSCH 525 and / or one or more repetitions of the PDSCH 525. The first transmission of a PDSCH 525 in a slot and the repetitions of the PDSCH 525 may use the same or different symbol configurations within the slot.
[0150] In a second example, the resource allocation scheme may correspond to a slot configuration 510. The slot configuration 510 illustrates an example in which an implicit starting symbol offset is indicated relative to each PDSCH repetition within a slot. This may include avoiding overlap of data symbols with DMRS symbols. The slot configuration 510 may include a PDCCH 520 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. The PDCCH 520 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 510). During the first two symbols after the PDCCH 520, the base station may transmit a data transmission by transmitting a DMRS 530 followed by a first transmission of a PDSCH 525 and one or more repetitions of the PDSCH 525 during the slot (two repetitions are shown by way of example only). In this example, one or more of the repetitions of the PDSCH 525 do not include another transmission of the DMRS 530.
[0151] In general, a data transmission may correspond to a PDSCH 525, each repetition of the PDSCH 525, and a DMRS 530. All available subbands in a supported BWP (e.g., a reduced bandwidth supported by the UE type) may be used to send the data transmission. Thus, the slot configuration 510 illustrates an example resource allocation scheme in which an implicit indication of a starting symbol is provided by introducing a downlink aggregation factor for PDSCH repetitions within a slot. The starting symbol of each PDSCH repetition may be implicitly indicated by selecting or otherwise using the first starting symbol (S) and the length (L) of the number of symbols in the DMRS symbol pattern or configuration. If all repeated PDSCH 525 repetitions share only the frontload DMRS, then S+L*index_rep may correspond to the starting symbol of each PDSCH 525 repetition. The first transmission of a PDSCH 525 in a slot and the repetitions of the PDSCH 525 may use the same or different symbol configurations in the slot. This may include identifying a first starting symbol for a first transmission of the PDSCH 525 and a second starting symbol for repeated transmissions of the PDSCH 525 based on an aggregation factor for intra-slot repetition.
[0152] In a third example, the resource allocation scheme may correspond to a slot configuration 515. The slot configuration 515 illustrates an example in which an implicit starting symbol offset is indicated relative to each PDSCH repetition within a slot. This may include avoiding overlap of data symbols with DMRS symbols. The slot configuration 515 may include a PDCCH 520 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. The PDCCH 520 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 515). During the first symbol following the PDCCH 520, the base station may transmit a data transmission by transmitting a DMRS 530 followed by a first transmission of a PDSCH 525 and one or more repetitions of the PDSCH 525 during the slot (two repetitions are shown by way of example only).
[0153] In this example, each repetition of PDSCH 525 includes another transmission of DMRS 530 (e.g., frontloaded DMRS) in the first symbol of the repetition. Broadly speaking, a data transmission can correspond to PDSCH 525, each repetition of PDSCH 525, and each transmission of DMRS 530. All available subbands in a supported BWP (e.g., a reduced bandwidth supported by the UE type) can be used to send the data transmission. Thus, slot configuration 515 illustrates an example resource allocation scheme in which an implicit indication of the starting symbol is provided by introducing a downlink aggregation factor for PDSCH 525 repetitions within a slot. The starting symbol of each PDSCH repetition can be implicitly indicated by selecting or otherwise using the first starting symbol (S) and the length (L) of the number of symbols and the DMRS symbol pattern. If each repeated PDSCH repetition uses the same DMRS pattern (as shown in slot configuration 515), then S+(L+D)*index_rep can correspond to the starting symbol of each PDSCH 525 repetition. The DMRS symbols within a slot can be correlated and jointly used for channel estimation.
[0154] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 505, 510, and / or 515.
[0155] Figure 6 An example time slot configuration set 600 is shown for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure. In some examples, the example time slot configuration set 600 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, 400, and / or 500. Aspects of the example time slot configuration set 600 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, aspects of the example time slot configuration set 600 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, aspects of the example time slot configuration set 600 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the example time slot configuration set 600 shows two examples of time slot configurations for supporting PDSCH enhancement for UE types with reduced capabilities.
[0156] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0157] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station) that carries or otherwise conveys an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.) or during registration (e.g., using NAS signals to a network entity) or thereafter.
[0158] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support inter-slot and / or intra-slot PDSCH repetitions. In some aspects, this can include each PDSCH repetition using the same frequency domain resource allocation. Example slot configuration set 600 shows two non-limiting examples of slot configurations that can be components of such resource allocation schemes according to various aspects of the described techniques.
[0159] In a first example, the resource allocation scheme may correspond to a slot configuration 605. The slot configuration 605 illustrates an example in which, when intra-slot repetition is configured, the UE may report its HARQ-ACK information after the last PDSCH in the aggregated PDSCH (e.g., the initial PDSCH transmission and each repetition) in the same slot. This may avoid requiring a short processing time for the UE. The slot configuration 605 may include a PDCCH 625 (e.g., a grant for downlink resources) transmitted in the first symbol of the slot. The PDCCH 625 may carry or otherwise transmit an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 605). During the first two symbols after the PDCCH 625, the base station may transmit data transmission by transmitting a DMRS 635 followed by a first transmission of a PDSCH 630 and one or more repetitions of the PDSCH 630 during the slot (two repetitions are shown by way of example only). The UE may then transmit its HARQ 610 in subsequent slots. The data transmission may correspond to the PDSCH 630, each repetition of the PDSCH 630, and the DMRS 635. The data transmission may be sent using all available subbands in a supported BWP (e.g., a reduced bandwidth supported by the UE type). Thus, the slot configuration 605 illustrates an example resource allocation scheme in which the UE may report its HARQ-ACK information (e.g., HARQ 610) after the last PDSCH 630 transmission or repetition. If the UE detects a PDSCH 630 with early termination (e.g., recovering data from the first PDSCH 630 transmission or using one of the earlier repetitions), the HARQ 610 timing may be counted from the end of the last PDSCH 630 repetition in the last slot in the aggregated PDSCH. Thus, the UE may send feedback signals (e.g., HARQ 610) for data transmission during subsequent slots. Subsequent slots may be configured with time gaps for processing and may be based on the slots in which the first PDSCH 630 and repeated PDSCH 630 transmissions were performed.
[0160] In a second example, the resource allocation scheme may correspond to a slot configuration 615. The slot configuration 615 illustrates an example where, when inter-slot repetition is configured in addition to inter-slot repetition, the UE may report its HARQ-ACK information after the last PDSCH in the last slot in the aggregated PDSCH (e.g., the initial PDSCH transmission and each repetition). This may avoid requiring a short processing time for the UE. The slot configuration 615 may include, in the first slot, a PDCCH 625 (e.g., a grant for downlink resources) transmitted in the first symbol of the first slot. The PDCCH 625 may carry or otherwise convey an indication of downlink resources according to the resource allocation scheme (e.g., according to the slot configuration 615). During the first two symbols following the PDCCH 625 in the first slot, the base station may transmit a data transmission by transmitting a DMRS 635 followed by a first transmission of a PDSCH 630 and one or more repetitions of the PDSCH 630 during the first slot (two repetitions are shown by way of example only). The slot configuration 615 may include, in the second slot, a PDCCH 625 (e.g., a grant for downlink resources), optionally transmitted in the first symbol of the second slot (e.g., the PDCCH 625 transmitted in the first slot may schedule data transmission in the second slot). The PDCCH 625 transmitted in the second slot may carry or otherwise convey an indication of downlink resources according to a resource allocation scheme (e.g., according to the slot configuration 615). During the first two symbols following the PDCCH 625 in the second slot, the base station may transmit a data transmission by transmitting a DMRS 635 followed by a first transmission of a PDSCH 630 and one or more repetitions of the PDSCH 630 during the second slot (two repetitions are shown by way of example only). The UE may then transmit its HARQ 620 in subsequent slots. The data transmission may correspond to an aggregated PDSCH 630 transmission, each repetition of the PDSCH 630, and the DMRS 635. Data transmissions may be sent using all available subbands in a supported BWP (eg, a reduced bandwidth supported by the UE type).
[0161] Thus, the slot configuration 615 illustrates an example resource allocation scheme in which a UE may report its HARQ-ACK information (e.g., HARQ 610) after the last PDSCH 630 transmission in the last slot in the aggregated PDSCH. If the UE can detect a PDSCH 630 with early termination (e.g., recovering data from the first PDSCH 630 transmission or one of the earlier repetitions), the HARQ 620 timing may be counted from the end of the last PDSCH 630 repetition in the last slot in the aggregated PDSCH. Thus, the slot configuration 615 may support one or more additional repetition transmissions of the data transmission in the second slot and a feedback signal (e.g., HARQ 620) provided during a subsequent slot having a time gap for processing by the UE based on the second slot in which the repetition transmission occurs.
[0162] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 605 and / or 610.
[0163] Figure 7 An example of a time slot configuration 700 for supporting PDSCH resources for UEs with reduced capabilities according to various aspects of the present disclosure is shown. In some examples, the time slot configuration 700 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, 400, 500, and / or 600. Various aspects of the time slot configuration 700 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, various aspects of the time slot configuration 700 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, various aspects of the time slot configuration 700 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the time slot configuration 700 shows an example of a time slot configuration for supporting PDSCH enhancement for UE types with reduced capabilities.
[0164] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not support these techniques. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0165] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station), the UE capability message carrying or otherwise conveying an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.), during registration (e.g., using NAS signals to a network entity), or the like.
[0166] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support inter-slot and / or intra-slot PDSCH repetitions. In some aspects, this can include each PDSCH repetition being allocated with different frequency domain resources in different slots. Slot configuration 700 illustrates a non-limiting example of such a resource allocation scheme according to aspects of the described techniques.
[0167] Slot configuration 700 illustrates an example where each PDSCH repetition can occur in a different slot and can use the same time domain resource allocation, but at different frequency domain locations depending on the frequency hopping pattern. Slot configuration 700 illustrates an example of configuring intra-slot BWP frequency hopping for each BWP, which can support or otherwise allow for different or the same frequency hopping patterns to be used in different BWPs. The frequency hopping pattern can be carried or otherwise communicated in RRC signaling, DCI, or the like.
[0168] The slot configuration 700 may include a PDCCH 710 transmitted in a first symbol of a first slot (e.g., for a grant of downlink resources). The PDCCH 710 may carry or otherwise convey an indication of downlink resources in accordance with a resource allocation scheme (e.g., in accordance with the slot configuration 700). During the first symbol following the PDCCH 710 in the first slot, the base station may transmit a data transmission by transmitting a DMRS 720 followed by a transmission of a PDSCH 715. The slot configuration 700 may optionally include a PDCCH 710 transmitted in a first symbol of a second slot (e.g., the PDCCH 710 transmitted in the first slot may schedule a data transmission in the second slot). When transmitted, the PDCCH 710 may carry or otherwise convey an indication of downlink resources in accordance with a resource allocation scheme (e.g., in accordance with the slot configuration 700). During the first symbol following the PDCCH 710 in the second slot, the base station may transmit a data transmission by transmitting a DMRS 720 followed by a repeated transmission of the PDSCH 715. The data transmission may correspond to the PDSCH 715, each repetition of the PDSCH 715, and the DMRS 720. The data transmission may be transmitted using a subset of the available subbands in the supported BWP (e.g., a reduced bandwidth supported by the UE type), with frequency hopping occurring for different slots.
[0169] Thus, slot configuration 700 illustrates an example resource allocation scheme where the downlink aggregation level per hop can be based, at least in some aspects, on the bundle size. This can also include providing an RB offset indication. Frequency hopping can result in foldback conditions (e.g., the starting and ending RBs can be located at two edges of a supported BWP). In some aspects, the timing position can be the same relative to the slot boundaries of each slot.
[0170] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to the time slot configuration 700.
[0171] Figure 8An example time slot configuration set 800 is shown that supports PDSCH resources for UEs with reduced capabilities in accordance with various aspects of the present disclosure. In some examples, the example time slot configuration set 800 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, 400, 500, 600, and / or time slot configuration 700. Various aspects of the example time slot configuration set 800 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, various aspects of the example time slot configuration set 800 can be implemented by a base station when the UE is operating in RRC connected mode, and / or various aspects of the example time slot configuration set 800 can be implemented in a network entity when the UE is operating in RRC inactive or RRC idle mode. Broadly speaking, the example time slot configuration set 800 shows possible examples of time slot configurations for supporting PDSCH enhancements for UE types with reduced capabilities.
[0172] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not support all such techniques. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0173] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station), the UE capability message carrying or otherwise conveying an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.), during registration (e.g., using NAS signals to a network entity), or the like.
[0174] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support inter-slot and / or intra-slot PDSCH repetitions. In some aspects, this can include each PDSCH repetition using different frequency domain resource allocations in different slots. Example slot configuration set 800 illustrates non-limiting examples of slot configurations that can be such resource allocation schemes according to various aspects of the described techniques.
[0175] In one example, the selected resource allocation scheme may correspond to a time slot configuration 805. Time slot configuration 805 illustrates an example in which each PDSCH repetition may occur in a different time slot and may use the same time domain resource allocation, but use different frequency domain locations in different BWPs based on a frequency hopping pattern. Time slot configuration 805 illustrates an example in which inter-BWP frequency hopping is configured for each BWP, which may support or otherwise allow for the use of different or the same frequency hopping patterns in different BWPs. The frequency hopping pattern may be carried or otherwise communicated in RRC signaling, DCI, or the like.
[0176] Slot configuration 805 may include a PDCCH 810 (e.g., a grant for downlink resources) transmitted in the first symbol of a first slot and in a first BWP (e.g., BWP 1). PDCCH 810 may carry or otherwise convey an indication of downlink resources according to a resource allocation scheme (e.g., according to slot configuration 805). During the first symbol following PDCCH 810 in the first slot and in the first BWP, the base station may transmit a data transmission by transmitting DMRS 820 followed by a transmission of PDSCH 815. Slot configuration 805 may optionally include a PDCCH 810 transmitted in the first symbol of a second slot and in a second BWP (e.g., BWP 2) (e.g., the PDCCH 810 transmitted in the first slot may schedule data transmission in the second slot). When transmitted, PDCCH 810 may carry or otherwise convey an indication of downlink resources according to a resource allocation scheme (e.g., according to slot configuration 805). During the first symbol following PDCCH 810 in the second time slot and the second BWP, the base station may transmit a data transmission by transmitting DMRS 820 followed by a repeated transmission of PDSCH 815. The data transmission may correspond to PDSCH 815, each repetition of PDSCH 815, and DMRS 820. The data transmission may be transmitted using a subset of the available subbands in the first and second BWPs (e.g., a reduced bandwidth supported by the UE type), with frequency hopping occurring for different time slots and in different BWPs. Thus, time slot configuration 805 illustrates an example resource allocation scheme in which the downlink aggregation level per hop may, at least in some aspects, be based on the bundle size.
[0177] In some examples, the slot configuration 805 may include a narrowband BWP offset indication (or BWP index sequence) that provides for inter-BWP frequency hopping. An NR light UE may be configured with more than one downlink BWP, where the total bandwidth size is no greater than the maximum bandwidth supported by the UE. The slot configuration 805 may maintain the same relative resource block position within the downlink BWP after frequency hopping. In some examples, the slot configuration 805 may support a floating narrowband BWP with a predefined hopping pattern. For example, an NR light UE may be configured with a downlink BWP of a size no greater than the UE's maximum supported bandwidth. The center frequency of the downlink BWP may be changed based on the frequency hopping pattern. In some examples, the time position relative to the slot boundary of each slot may be the same.
[0178] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to a timeslot configuration 805.
[0179] Figure 9 An example time slot configuration set 900 is shown that supports PDSCH resources for UEs with reduced capabilities according to various aspects of the present disclosure. In some examples, the example time slot configuration set 900 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, 400, 500, 600, and / or 800, and / or the example time slot configuration 700. Aspects of the example time slot configuration set 900 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, when the UE is operating in RRC connected mode, aspects of the example time slot configuration set 900 can be implemented by the base station, and / or when the UE is operating in RRC inactive or RRC idle mode, aspects of the example time slot configuration set 900 can be implemented in the network entity. In another example, the UE can report the capability to the network entity (e.g., to the MME via NAS signaling). The base station implements the UE's features based on relevant information obtained from the network entity. Broadly speaking, the example slot configuration set 900 illustrates two examples of slot configurations for PDSCH enhancement to support UE types with reduced capabilities.
[0180] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0181] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station), the UE capability message carrying or otherwise conveying an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.), during registration (e.g., using NAS signals to a network entity), or the like.
[0182] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support inter-slot and / or intra-slot PDSCH repetitions. In some aspects, this can include each PDSCH repetition using different frequency domain resource allocations in different slots. Example slot configuration set 900 shows two non-limiting examples of slot configurations that can be components of such resource allocation schemes according to various aspects of the described techniques.
[0183] In a first example, the selected resource allocation scheme may correspond to a timeslot configuration 905. Timeslot configuration 905 illustrates an example in which each PDSCH repetition may occur in a different timeslot and may use the same time-domain resource allocation, but utilize different frequency-domain locations in different BWPs based on a frequency hopping pattern. Timeslot configuration 905 illustrates an example of configuring inter-BWP frequency hopping for each BWP, which may support or otherwise allow for the use of different or the same frequency hopping patterns in different BWPs. An indication of the frequency hopping pattern may be carried or otherwise communicated in RRC signaling, DCI, or the like. Timeslot configuration 905 also illustrates an example of providing a retuning gap in the downlink. Radio frequency (RF) retuning may be required due to frequency hopping (e.g., if RF retuning is required for inter-BWP frequency hopping or dual connectivity (DC) changes). The retuning gap (e.g., a guard period) for RF retuning may be configured in two (or more) options. Slot configuration 905 shows a first example in which symbols at the beginning of a slot after a frequency hop (e.g., symbols typically reserved for downlink control information (e.g., PDCCH)) are used as a retuning gap. In this example, symbols typically allocated for downlink control information may be used for the retuning gap unless the control information is co-located with the retuning gap region. Therefore, it may not be desirable for the UE to monitor / transmit signals during the retuning gap during frequency hopping.
[0184] Thus, slot configuration 905 may include a retuning gap 910 in the first symbol of a first slot and in a first BWP (e.g., BWP 1). The UE may use retuning gap 910 to retune to the subband on which the data transmission is scheduled. Following retuning gap 910 in the first slot and the first BWP, the base station may transmit a data transmission by transmitting a PDSCH 915 in the first subband and the first BWP. Slot configuration 905 may include retuning gap 910 transmitted in the first symbol of a second slot and in the second BWP. During the first symbol following retuning gap 910 in the second slot and the second BWP (e.g., BWP 2), the base station may transmit a data transmission by transmitting a repeated transmission of PDSCH 915. The data transmission may correspond to PDSCH 915 and any repeated transmission of PDSCH 915. The data transmission may be transmitted using a subset of the available subbands in the first and second BWPs (e.g., a reduced bandwidth supported by the UE type), with frequency hopping occurring for different slots and in different BWPs.
[0185] In a second example, the resource allocation scheme may correspond to a timeslot configuration 920. Timeslot configuration 920 illustrates an example in which each PDSCH repetition may occur in a different timeslot and may use the same time-domain resource allocation, but utilize different frequency-domain locations in different BWPs based on a frequency hopping pattern. Timeslot configuration 920 illustrates an example of configuring inter-BWP frequency hopping for each BWP, which may support or otherwise allow for the use of different or the same frequency hopping patterns in different BWPs. An indication of the frequency hopping pattern may be carried or otherwise communicated in RRC signaling, DCI, or the like. Timeslot configuration 920 also illustrates an example of providing a retuning gap in the downlink. The RF retuning gap may be due to frequency hopping (e.g., if RF retuning is required for inter-BWP frequency hopping or DC changes). The retuning gap (e.g., guard period) used for RF retuning may be configured as two (or more) options. Slot configuration 920 shows a second example where symbols are at the end of the slot after frequency hopping (e.g., symbols typically reserved for uplink control information (e.g., PUCCH)). In this example, symbols typically allocated for uplink control information may be used for the retuning gap unless the control information is co-located with the retuning gap region. Therefore, it may not be desirable for the UE to monitor / transmit signals during the retuning gap during frequency hopping.
[0186] Thus, slot configuration 920 may begin with a data transmission (e.g., PDSCH 915) occurring first in a first slot, using a first subband, and in a first BWP. Slot configuration 920 may include a retuning gap 910 in the first symbol of the first slot and in a first BWP (e.g., BWP 1). The UE may use retuning gap 910 to retun to the subband on which the data transmission is scheduled in the second slot. Following retuning gap 910 in the first slot and the first BWP, the base station may transmit a data transmission by performing a repeated transmission of PDSCH 915 in a second subband and a second BWP (e.g., BWP 2). Slot configuration 920 may include retuning gap 910 transmitted in the last symbol of the second slot and in the second BWP. The data transmission may correspond to PDSCH 915 and any repeated transmissions of PDSCH 915. The data transmission may be transmitted using a subset of the available subbands in the first and second BWPs (e.g., a reduced bandwidth supported by the UE type), with frequency hopping occurring for different slots and in different BWPs. The symbols at the end of the time slot that occurred before the frequency hopping (eg, symbols typically reserved for uplink control information) may be reused for the retuning gap 910 .
[0187] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 905 and / or 920.
[0188] Figure 10 An example time slot configuration set 1000 is shown that supports PDSCH resources for UEs with reduced capabilities in accordance with various aspects of the present disclosure. In some examples, the example time slot configuration set 1000 can implement aspects of the wireless communication system 100 and / or the example time slot configuration sets 200, 300, 400, 500, 600, 800, and / or 900, and / or the example time slot configuration 700. Aspects of the example time slot configuration set 1000 can be implemented by a UE, a base station, and / or a network entity (e.g., an MME) (which can be examples of corresponding devices described herein). Specifically, aspects of the example time slot configuration set 1000 can be implemented by a base station when the UE is operating in RRC connected mode, and / or aspects of the example time slot configuration set 1000 can be implemented in a network entity when the UE is operating in RRC inactive or RRC idle mode. Broadly speaking, the example time slot configuration set 1000 illustrates two examples of time slot configurations for supporting PDSCH enhancement for UE types with reduced capabilities.
[0189] As described above, some wireless communication systems may utilize various frequency, time, and / or space diversity techniques to improve system throughput and performance. While some UE types support such diversity schemes, other UE types may not. For example, some UE types may be associated with UEs with reduced or limited capabilities (e.g., reduced bandwidth, fewer antennas, or extended battery life). Therefore, references to UE types herein generally refer to these UEs with reduced capabilities.
[0190] Thus, aspects of the described techniques provide various mechanisms for enhancing communications for such UE types (e.g., reduced capability UE types). For example, a UE may send or otherwise provide a UE capability message to a base station (and / or to a network entity via the base station), the UE capability message carrying or otherwise conveying an indication of the UE type of the UE. As discussed, the UE type may be associated with, for example, a reduced capability UE having reduced bandwidth, a reduced number of antennas, a low transmit power level, little or no mobility, enhanced power savings / extended battery life. The UE capability message may be provided during initial connection (e.g., using one or more RRC signals, MAC CEs, etc.) or during registration (e.g., using NAS signals to a network entity).
[0191] A base station (or network entity) can typically select a resource allocation scheme for a UE that can be used to send downlink grants and / or data transmissions to the UE based on the UE type. In some aspects, the described techniques can support inter-slot and / or intra-slot PDSCH repetitions. In some aspects, this can include each PDSCH repetition using different frequency domain resource allocations in different slots. Example slot configuration set 1000 shows two non-limiting examples of slot configurations that can be components of such resource allocation schemes according to various aspects of the described techniques.
[0192] In a first example, the resource allocation scheme may correspond to a timeslot configuration 1005. Timeslot configuration 1005 illustrates an example in which each PDSCH repetition may occur in a different timeslot, and the same or different time-domain resource allocations may be used between timeslots, and the same or different frequency domain locations may be used between timeslots and within the same BWP, depending on the frequency hopping pattern. Timeslot configuration 1005 illustrates an example of configuring inter-slot repetition and inter-BWP frequency hopping for each BWP, which may support or otherwise allow the use of different or the same frequency hopping patterns in different BWPs. An indication of the frequency hopping pattern may be carried or otherwise communicated in RRC signaling, DCI, or the like. Timeslot configuration 1005 also illustrates an example including PDSCH repetition / aggregation and frequency hopping. A single DCI may be used to schedule multi-slot PDSCH frequency hopping. Redundancy version (RV) repetition may be used with a predefined sequence applied to the same hopping frequency and / or different hopping frequencies. In addition to frequency hopping, an RRC-configured downlink aggregation factor may also be used for multi-slot repetition. The RV pattern may be repeated in four time slots, such as RV2, RV3, RV1 and RV0 or some other pattern.
[0193] Thus, slot configuration 1005 may begin with the base station transmitting a PDCCH 1015 in the first symbol of the first slot and in the first BWP (e.g., BWP 1). PDCCH 1015 may carry or otherwise convey an indication of a downlink grant (e.g., DCI) scheduling a data transmission (e.g., PDSCH 1020). PDCCH 1015 may be transmitted throughout the entire BWP. The base station may then perform data transmission by transmitting PDSCH 1020 in the remaining symbols of the first slot. In the second slot, the base station may again transmit PDCCH 1015 in the first symbol of the second slot, followed by repeated transmissions of PDSCH 1020 in the remaining symbols of the second slot and in the first BWP. In the third slot, the base station may again transmit PDCCH 1015 in the first symbol of the third slot, followed by repeated transmissions of PDSCH 1020 in the remaining symbols of the third slot. In the fourth time slot, the base station may again transmit PDCCH 1015 in the first symbol of the fourth time slot, followed by repeated transmission of PDSCH 1020 in the remaining symbols of the fourth time slot. The PDSCH 1020 transmission in each of the four time slots may use the same frequency domain resource allocation (e.g., on the same subband). That is, the time slot bundling / aggregation technique may be used in each frequency hop and may be repeated at the same frequency position before the frequency hop. In some examples, DMRS (not shown) with the same frequency domain resource allocation may be associated within each (or all) hops. Data transmission may correspond to PDSCH 1020 and any repeated transmission of PDSCH 1020.
[0194] In a second example, the resource allocation scheme may correspond to a timeslot configuration 1010. Timeslot configuration 1010 illustrates an example in which each PDSCH repetition may occur in a different timeslot, and the same or different time-domain resource allocations may be used between timeslots, with different frequency domain locations being used between timeslots and within different BWPs depending on the frequency hopping pattern. Timeslot configuration 1010 illustrates an example of configuring inter-slot repetition and inter-BWP frequency hopping for each BWP, which may support or otherwise allow for the use of different or the same frequency hopping patterns within different BWPs. An indication of the frequency hopping pattern may be carried or otherwise communicated in RRC signaling, DCI, or the like. Timeslot configuration 1010 also illustrates an example including PDSCH repetition / aggregation and frequency hopping. A single DCI may be used to schedule multi-slot PDSCH frequency hopping. RV repetition may be used with a predefined sequence that applies to the same hopping frequency and / or different hopping frequencies. In addition to frequency hopping, an RRC-configured downlink aggregation factor may also be used for multi-slot repetition. The RV pattern may be repeated in four time slots, such as RV2, RV3, RV1 and RV0 or some other pattern.
[0195] Thus, slot configuration 1010 may begin with the base station transmitting a PDCCH 1015 in the first symbol of the first slot and in the first BWP (e.g., BWP 1). PDCCH 1015 may carry or otherwise convey an indication of a downlink grant (e.g., DCI) scheduling a data transmission (e.g., PDSCH 1020). PDCCH 1015 may be transmitted in the entire BWP. The base station may then perform data transmission by transmitting PDSCH 1020 in the remaining symbols of the first slot and on the first subband. In the second slot, still in the first BWP, the base station may again use the entire BWP to transmit PDCCH 1015 in the first symbol of the second slot, followed by repeated transmissions of PDSCH 1020 in the remaining symbols of the second slot and in the first BWP on the first subband. In the third time slot, the base station may again transmit PDCCH 1015 in the first symbol of the third time slot in the second BWP, using the second entire BWP, followed by repeated transmissions of PDSCH 1020 in the remaining symbols of the third time slot in the second BWP and using the second subband. In the fourth time slot, the base station may again transmit PDCCH 1015 in the first symbol of the fourth time slot in the second BWP, using the entire BWP, followed by repeated transmissions of PDSCH 1020 in the remaining symbols of the fourth time slot in the second BWP and on the second subband. PDSCH 1020 transmissions in each pair of time slots in the four time slots may use the same frequency-domain resource allocation (e.g., on the same subband). That is, time slot bundling / aggregation techniques may be used in each frequency hop and may be repeated at the same frequency location before the frequency hop. In some examples, DMRS (not shown) with the same frequency-domain resource allocation may be associated within each (or all) hops. Data transmissions may correspond to PDSCH 1020 and any repeated transmissions of PDSCH 1020.
[0196] Thus, the UE and the base station may transmit downlink grants and corresponding downlink data transmissions scheduled by the downlink grants according to the resource allocation scheme.The resource allocation scheme may correspond to one or more of the time slot configurations 1005 and / or 1010.
[0197] Figure 11 A block diagram 1100 of a device 1105 supporting PDSCH resources for reduced-capability UEs according to aspects of the present disclosure is shown. The device 1105 can be an example of aspects of the UE 115 as described herein. The device 1105 can include a receiver 1110, a communication manager 1115, and a transmitter 1120. The device 1105 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0198] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to PDSCH resources for UEs with reduced capabilities). The information may be communicated to other components of the device 1105. The receiver 1110 may be a reference Figure 14 Examples of various aspects of the transceiver 1420 are described. The receiver 1110 may utilize a single antenna or a collection of antennas.
[0199] The communication manager 1115 may perform the following operations: sending a UE capability message to the base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capability message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion of the UE; monitoring a wireless channel based on the downlink grant; and receiving a data transmission based on the monitoring of the wireless channel. The communication manager 1115 may be an example of aspects of the communication manager 1410 described herein.
[0200] The communication manager 1115 or its subcomponents may be implemented in hardware, in code (e.g., software) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1115 or its subcomponents may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this disclosure.
[0201] The communication manager 1115 or its subcomponents can be physically located at various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1115 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1115 or its subcomponents can be combined with one or more other hardware components (including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).
[0202] The transmitter 1120 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1120 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1120 may be a reference Figure 14Examples of aspects of the transceiver 1420 are described. The transmitter 1120 may utilize a single antenna or a collection of antennas.
[0203] Figure 12 A block diagram 1200 of a device 1205 supporting PDSCH resources for reduced-capability UEs according to aspects of the present disclosure is shown. The device 1205 can be an example of aspects of the device 1105 or UE 115 as described herein. The device 1205 can include a receiver 1210, a communication manager 1215, and a transmitter 1235. The device 1205 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0204] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to PDSCH resources for UEs with reduced capabilities). The information may be communicated to other components of the device 1205. The receiver 1210 may be a reference Figure 14 Examples of various aspects of the transceiver 1420 are described. The receiver 1210 may utilize a single antenna or a collection of antennas.
[0205] Communications manager 1215 may be an example of aspects of communications manager 1115 as described herein. Communications manager 1215 may include UE capability manager 1220, authorization manager 1225, and data transfer manager 1230. Communications manager 1215 may be an example of aspects of communications manager 1410 as described herein.
[0206] The UE capability manager 1220 may send a UE capability message to the base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE.
[0207] The grant manager 1225 may receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capability message, wherein the resource allocation scheme is associated with the UE type and the supported bandwidth portion of the UE; and monitor the wireless channel based on the downlink grant.
[0208] The data transmission manager 1230 may receive data transmissions based on monitoring of the wireless channel.
[0209] The transmitter 1235 can transmit signals generated by other components of the device 1205. In some examples, the transmitter 1235 can be co-located with the receiver 1210 in a transceiver module. For example, the transmitter 1235 can be a reference Figure 14Examples of various aspects of the transceiver 1420 are described. The transmitter 1235 can utilize a single antenna or a collection of antennas.
[0210] Figure 13 A block diagram 1300 of a communication manager 1305 supporting PDSCH resources for reduced-capability UEs in accordance with aspects of the present disclosure is shown. The communication manager 1305 can be an example of aspects of the communication manager 1115, the communication manager 1215, or the communication manager 1410 described herein. The communication manager 1305 can include a UE capability manager 1310, a grant manager 1315, a data transmission manager 1320, an interleaving manager 1325, a BWP manager 1330, a repetition manager 1335, a slot manager 1340, and a repetition / slot index manager 1345. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).
[0211] The UE capability manager 1310 may send a UE capability message to the base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE.
[0212] Grant manager 1315 may receive a downlink grant for downlink resources for data transmission based on a resource allocation scheme based on the UE capability message, wherein the resource allocation scheme is associated with the UE type and the supported bandwidth portion of the UE. In some examples, grant manager 1315 may monitor the wireless channel based on the downlink grant.
[0213] Data transmission manager 1320 may receive data transmissions based on monitoring of wireless channels.
[0214] Interlace manager 1325 may receive data transmissions in interleaved and non-contiguous resource blocks distributed across a subset of the available subbands in the supported BWP, the subset being based on the UE type.
[0215] The BWP manager 1330 may receive data transmissions on supported BWPs and using a low coding rate, which is based on the UE type.
[0216] In some examples, the BWP manager 1330 can identify a scaling factor for data transmission using a low coding rate based on a scaling factor of a transmit block size, the scaling factor being based on a UE type. In some cases, a first DMRS transmission is transmitted during a first time period in a first portion of a time slot. In some cases, a second DMRS transmission is transmitted during a second time period in a second portion of a time slot, the first time period in the first portion of the time slot being different from the second time period in the second portion of the time slot.
[0217] Repeat manager 1335 may receive a first transmission of a data transmission and repeated transmissions of the data transmission in a time slot.
[0218] In some examples, repetition manager 1335 may identify a DMRS configuration for receiving a first transmission and a repeat transmission in a timeslot. In some examples, repetition manager 1335 may receive the data transmission based on the DMRS configuration. In some examples, repetition manager 1335 may receive the first DMRS transmission during a first portion of the timeslot for the first transmission and the second DMRS transmission during a second portion of the timeslot for the repeat transmission. In some examples, repetition manager 1335 may identify a first starting symbol for the first transmission and a second starting symbol for the repeat transmission based on a downlink aggregation factor for data repetition within the timeslot.
[0219] In some examples, repetition manager 1335 may transmit a feedback signal for the data transmission during a subsequent time slot having a time gap for processing, based on the time slot in which the first transmission and the repetition transmission were received. In some examples, repetition manager 1335 may receive one or more additional repetition transmissions of the data transmission in a second time slot that occurs after the time slot in which the first transmission and the repetition transmission were received. In some examples, repetition manager 1335 may transmit a feedback signal during a subsequent time slot having a time gap for processing, based on the second time slot in which the one or more repetition transmissions may be received. In some cases, the first DMRS transmission is received during an initial time period of a first portion of a time slot. In some cases, the second DMRS transmission is received during an initial time period of a second portion of a time slot. In some cases, the first DMRS transmission is received during a first time period of a first portion of a time slot for the first transmission. In some cases, the second DMRS transmission is received during a second time period of a second portion of a time slot for the repetition transmission, the first time period of the first portion of the time slot being different from the second time period of the second portion of the time slot. In some cases, the first transmission and the repetition transmission occur during the same symbol configuration or different symbol configurations in the time slot.
[0220] The slot manager 1340 may receive a first portion of the data transmission in a first time slot on a first subband supporting a BWP. In some examples, the slot manager 1340 may receive a second portion of the data transmission in a second time slot on a second subband supporting a BWP, where the first subband is a different subband from the second subband. In some examples, the slot manager 1340 may receive the first portion of the data transmission and the second portion of the data transmission based on the same time domain configuration or different time domain configurations between the first time slot and the second time slot. In some examples, the slot manager 1340 may determine that the first subband is in a first BWP and the second subband is in a second BWP different from the first BWP. In some examples, the slot manager 1340 may perform a retuning operation during a retuning gap between receiving the first portion and receiving the second portion. In some examples, the slot manager 1340 may receive the first portion in the first time slot and the second portion in the second time slot based on RVs associated with the first and second portions of the data transmission.
[0221] In some cases, the first subband and the second subband are in the same BWP or in different BWPs. In some cases, the retuning gap is the last portion of the first subband in the first BWP, or the first portion of the second subband in the second BWP, or a combination thereof.
[0222] The repetition / slot index manager 1345 may receive data transmissions based on a slot index, a repetition index, or a combination thereof.
[0223] Figure 14 A diagram of a system 1400 including a device 1405 supporting PDSCH resources for reduced-capability UEs in accordance with aspects of the present disclosure is shown. The device 1405 may be an example of, or include components of, the device 1105, device 1205, or UE 115 as described herein. The device 1405 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1410, an I / O controller 1415, a transceiver 1420, an antenna 1425, a memory 1430, and a processor 1440. These components may communicate electronically via one or more buses, such as a bus 1445.
[0224] The communication manager 1410 can perform the following operations: sending a UE capability message to the base station, the UE capability message including an indication of the UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, or a reduced number of antennas, or a combination thereof; based on the UE capability message, receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme, wherein the resource allocation scheme is associated with the UE type and the supported bandwidth portion of the UE; monitoring the wireless channel based on the downlink grant; and receiving data transmission based on the monitoring of the wireless channel.
[0225] I / O controller 1415 can manage input and output signals for device 1405. I / O controller 1415 can also manage peripheral devices that are not integrated into device 1405. In some cases, I / O controller 1415 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1415 can utilize a computer such as , or another known operating system. In other cases, I / O controller 1415 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1415 may be implemented as part of a processor. In some cases, a user may interact with device 1405 via I / O controller 1415 or via hardware components controlled by I / O controller 1415.
[0226] The transceiver 1420 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1420 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1420 can also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna.
[0227] In some cases, a wireless device may include a single antenna 1425. However, in some cases, the device may have more than one antenna 1425 that are capable of sending or receiving multiple wireless transmissions simultaneously.
[0228] Memory 1430 may include random access memory (RAM) and read-only memory (ROM). Memory 1430 may store computer-readable, computer-executable code 1435, which includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1430 may also contain, among other things, a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0229] The processor 1440 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1440 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1440. The processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks that support PDSCH resources for UEs with reduced capabilities).
[0230] The code 1435 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1435 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, the code 1435 may not be directly executable by the processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0231] Figure 15 A block diagram 1500 of a device 1505 supporting PDSCH resources for reduced-capability UEs according to aspects of the present disclosure is shown. The device 1505 can be an example of aspects of the base station 105 as described herein. The device 1505 can include a receiver 1510, a communication manager 1515, and a transmitter 1520. The device 1505 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0232] The receiver 1510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to PDSCH resources for UEs with reduced capabilities). The information may be communicated to other components of the device 1505. The receiver 1510 may be a reference Figure 18 Examples of various aspects of the transceiver 1820 are described. The receiver 1510 may utilize a single antenna or a collection of antennas.
[0233] The communication manager 1515 may perform the following operations: receiving a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; selecting a resource allocation scheme for a downlink grant for the UE based on the UE capability message and the supported bandwidth portion of the UE; sending a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme; and sending a data transmission to the UE based on the downlink grant. The communication manager 1515 may be an example of aspects of the communication manager 1810 described herein.
[0234] The communication manager 1515 or its subcomponents may be implemented in hardware, in code (e.g., software) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1515 or its subcomponents may be performed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.
[0235] The communication manager 1515 or its subcomponents can be physically located in various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1515 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1515 or its subcomponents can be combined with one or more other hardware components (including but not limited to I / O components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).
[0236] The transmitter 1520 may transmit signals generated by other components of the device 1505. In some examples, the transmitter 1520 may be co-located with the receiver 1510 in a transceiver module. For example, the transmitter 1520 may be a reference Figure 18 Examples of various aspects of the transceiver 1820 are described. The transmitter 1520 may utilize a single antenna or a collection of antennas.
[0237] Figure 16A block diagram 1600 of a device 1605 supporting PDSCH resources for reduced-capability UEs according to aspects of the present disclosure is shown. The device 1605 can be an example of aspects of the device 1505 or base station 105 as described herein. The device 1605 may include a receiver 1610, a communication manager 1615, and a transmitter 1640. The device 1605 may also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0238] The receiver 1610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to PDSCH resources for UEs with reduced capabilities). The information may be communicated to other components of the device 1605. The receiver 1610 may be a reference Figure 18 Examples of various aspects of the transceiver 1820 are described. The receiver 1610 may utilize a single antenna or a group of antennas.
[0239] The communication manager 1615 may be an example of aspects of the communication manager 1515 as described herein. The communication manager 1615 may include a UE capability manager 1620, a resource allocation scheme manager 1625, an authorization manager 1630, and a data transfer manager 1635. The communication manager 1615 may be an example of aspects of the communication manager 1810 as described herein.
[0240] The UE capability manager 1620 may receive a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE.
[0241] The resource allocation scheme manager 1625 may select a resource allocation scheme for a downlink grant for a UE based on the UE capability message and the supported bandwidth portion of the UE.
[0242] Grant manager 1630 may send a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme.
[0243] The data transmission manager 1635 may send a data transmission to the UE based on the downlink grant.
[0244] The transmitter 1640 can transmit signals generated by other components of the device 1605. In some examples, the transmitter 1640 can be co-located with the receiver 1610 in a transceiver module. For example, the transmitter 1640 can be a reference Figure 18 Examples of aspects of the transceiver 1820 are described. The transmitter 1640 may utilize a single antenna or a collection of antennas.
[0245] Figure 17 A block diagram 1700 is shown of a communication manager 1705 that supports PDSCH resources for reduced-capability UEs in accordance with aspects of the present disclosure. The communication manager 1705 can be an example of aspects of the communication manager 1515, the communication manager 1615, or the communication manager 1810 described herein. The communication manager 1705 can include a UE capability manager 1710, a resource allocation scheme manager 1715, a grant manager 1720, a data transmission manager 1725, an interleaving manager 1730, a BWP manager 1735, a repetition manager 1740, a slot manager 1745, and a repetition / slot index manager 1750. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).
[0246] The UE capability manager 1710 may receive a UE capability message from a UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE.
[0247] The resource allocation scheme manager 1715 may select a resource allocation scheme for a downlink grant for a UE based on the UE capability message and the supported bandwidth portion of the UE.
[0248] Grant manager 1720 may send a downlink grant to the UE for downlink resources for data transmission according to the resource allocation scheme.
[0249] The data transmission manager 1725 may send a data transmission to the UE based on the downlink grant.
[0250] Interlace manager 1730 may send data transmissions in interleaved and non-contiguous resource blocks distributed across a subset of the available subbands in the supported BWP, the subset being based on the UE type.
[0251] The BWP manager 1735 may send data transmissions on supported BWPs and using a low coding rate that is based on the UE type.
[0252] In some examples, the BWP manager 1735 can identify a scaling factor to use for data transmission using a low coding rate based on a scaling factor of the transmit block size, the scaling factor being based on the UE type.
[0253] Repetition manager 1740 may send a first transmission of a data transmission and a repeated transmission of the data transmission in a time slot. In some examples, repetition manager 1740 may identify a DMRS configuration for sending the first transmission and the repeated transmission in the time slot. In some examples, repetition manager 1740 may send the data transmission based on the DMRS configuration. In some examples, repetition manager 1740 may send the first DMRS transmission during a first portion of the time slot for the first transmission and send the second DMRS transmission during a second portion of the time slot for the repeated transmission. In some examples, repetition manager 1740 may identify a first starting symbol for the first transmission and a second starting symbol for the repeated transmission based on a downlink aggregation factor for data repetition within the time slot. In some examples, repetition manager 1740 may receive a feedback signal for the data transmission during a subsequent time slot having a time gap for processing based on the time slot in which the first transmission and the repeated transmission were sent.
[0254] In some examples, repetition manager 1740 may transmit one or more additional repetitions of the data transmission in a second time slot that occurs after the time slot in which the first transmission and the repetition transmission were transmitted. In some examples, repetition manager 1740 may receive a feedback signal during a subsequent time slot having a time gap for processing based on the second time slot in which the one or more repetition transmissions may be transmitted. In some cases, the first DMRS transmission is transmitted during an initial time period of a first portion of the time slot for the first transmission. In some cases, the second DMRS transmission is transmitted during an initial time period of a second portion of the time slot for the repetition transmission. In some cases, the first transmission and the repetition transmission occur during the same symbol configuration or different symbol configurations in the time slot.
[0255] The slot manager 1745 may transmit a first portion of the data transmission in a first time slot and on a first subband supporting a BWP. In some examples, the slot manager 1745 may transmit a second portion of the data transmission in a second time slot on a second subband supporting a BWP, where the first subband is a different subband from the second subband. In some examples, the slot manager 1745 may transmit the first and second portions of the data transmission according to the same time domain configuration or different time domain configurations between the first and second time slots. In some examples, the slot manager 1745 may determine that the first subband is in a first BWP and the second subband is in a second BWP different from the first BWP. In some examples, the slot manager 1745 may configure a retuning gap between transmitting the first portion and receiving the second portion. In some examples, the slot manager 1745 may transmit the first portion in the first time slot and the second portion in the second time slot based on RVs associated with the first and second portions of the data transmission.
[0256] In some cases, the first subband and the second subband are in the same BWP or in different BWPs. In some cases, the retuning gap includes the last portion of the first subband in the first BWP, or the first portion of the second subband in the second BWP, or a combination thereof.
[0257] The repetition / slot index manager 1750 may send data transmissions based on the slot index, the repetition index, or a combination thereof.
[0258] Figure 18 A diagram of a system 1800 including a device 1805 supporting PDSCH resources for reduced-capability UEs in accordance with aspects of the present disclosure is shown. The device 1805 may be an example of, or include components of, a device 1505, a device 1605, or a base station 105 as described herein. The device 1805 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communications manager 1810, a network communications manager 1815, a transceiver 1820, an antenna 1825, a memory 1830, a processor 1840, and an inter-station communications manager 1845. These components may communicate electronically via one or more buses, such as a bus 1850.
[0259] The communication manager 1810 can perform the following operations: receive a UE capability message from the UE, the UE capability message including an indication of the UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, or a reduced number of antennas, or a combination thereof; select a resource allocation scheme for a downlink grant for the UE based on the UE capability message and the supported bandwidth portion of the UE; send a downlink grant for downlink resources for data transmission to the UE according to the resource allocation scheme; and send data transmission to the UE based on the downlink grant.
[0260] The network communications manager 1815 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1815 may manage the transmission of data communications for client devices (eg, one or more UEs 115).
[0261] The transceiver 1820 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1820 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1820 can also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna.
[0262] In some cases, a wireless device may include a single antenna 1825. However, in some cases, the device may have more than one antenna 1825 that are capable of sending or receiving multiple wireless transmissions simultaneously.
[0263] Memory 1830 may include RAM, ROM, or a combination thereof. Memory 1830 may store computer-readable code 1835, which includes instructions that, when executed by a processor (e.g., processor 1840), cause device 1805 to perform various functions described herein. In some cases, memory 1830 may also contain, among other things, BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.
[0264] The processor 1840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1840 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1840. The processor 1840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1830) to cause the device 1805 to perform various functions (e.g., functions or tasks that support PDSCH resources for UEs with reduced capabilities).
[0265] The inter-site communication manager 1845 can manage communications with other base stations 105 and can include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-site communication manager 1845 can coordinate the scheduling of transmissions to the UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1845 can provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communications between the base stations 105.
[0266] The code 1835 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1835 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, the code 1835 may not be directly executable by the processor 1840, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.
[0267] Figure 19A flow chart illustrating a method 1900 for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by the UE 115 or components thereof as described herein. For example, the operations of the method 1900 may be implemented by the UE 115 or components thereof as described herein. Figures 11 to 14 In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.
[0268] At 1905, the UE may send a UE capability message to the base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, a reduced number of antennas, or a combination thereof. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be as described with reference to Figures 11 to 14 The UE capability manager described in this document is used to perform the following operations:
[0269] At 1910, the UE may receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capability message, wherein the resource allocation scheme is associated with the UE type and the supported bandwidth portion of the UE. The operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be as described with reference to Figures 11 to 14 Describes the authorization manager to perform.
[0270] At 1915, the UE may monitor the wireless channel based on the downlink grant. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be as described with reference to Figures 11 to 14 Describes the authorization manager to perform.
[0271] At 1920, the UE may receive data transmission based on monitoring of the wireless channel. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be as described with reference to Figures 11 to 14 Describes the data transfer manager to perform.
[0272] Figure 20 A flow chart illustrating a method 2000 for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by the UE 115 or components thereof as described herein. For example, the operations of the method 2000 may be implemented by the UE 115 or components thereof as described herein. Figures 11 to 14In some examples, the UE may execute an instruction set to control the functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.
[0273] At 2005, the UE may send a UE capability message to the base station, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, a reduced number of antennas, or a combination thereof. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described with reference to Figures 11 to 14 The UE capability manager described in this document is used to perform the following operations:
[0274] At 2010, the UE may receive a downlink grant for downlink resources for data transmission according to a resource allocation scheme based on the UE capability message, wherein the resource allocation scheme is associated with the UE type and the supported bandwidth portion of the UE. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Figures 11 to 14 Describes the authorization manager to perform.
[0275] At 2015, the UE may monitor the wireless channel based on the downlink grant. The operations of 2015 may be performed according to the methods described herein. In some examples, aspects of the operations of 2015 may be as described with reference to Figures 11 to 14 Describes the authorization manager to perform.
[0276] At 2020, the UE may receive data transmission based on monitoring of the wireless channel. The operations of 2020 may be performed according to the methods described herein. In some examples, aspects of the operations of 2020 may be as described with reference to Figures 11 to 14 Describes the data transfer manager to perform.
[0277] At 2025, the UE may receive data transmissions in interleaved and non-contiguous resource blocks distributed across a subset of available subbands in a supported BWP, the subset being based on UE type. The operations of 2025 may be performed according to the methods described herein. In some examples, aspects of the operations of 2025 may be as described with reference to Figures 11 to 14 The described interleaving manager is used to perform the
[0278] Figure 21 A flow chart illustrating a method 2100 for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of the method 2100 may be implemented by the base station 105 or components thereof as described herein. Figures 15 to 18In some examples, the base station may execute an instruction set to control the functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.
[0279] At 2105, the base station may receive a UE capability message from the UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, a reduced number of antennas, or a combination thereof. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Figures 15 to 18 The UE capability manager described in this document is used to perform the following operations:
[0280] At 2110, the base station may select a resource allocation scheme for a downlink grant for the UE based on the UE capability message and the supported bandwidth portion of the UE. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be as described with reference to Figures 15 to 18 Describes the resource allocation scheme manager to perform.
[0281] At 2115, the base station may send a downlink grant for downlink resources for data transmission to the UE according to the resource allocation scheme. The operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be as described with reference to Figures 15 to 18 Describes the authorization manager to perform.
[0282] At 2120, the base station may send a data transmission to the UE based on the downlink grant. The operations of 2120 may be performed according to the methods described herein. In some examples, aspects of the operations of 2120 may be as described with reference to Figures 15 to 18 Describes the data transfer manager to perform.
[0283] Figure 22 A flow chart illustrating a method 2200 for supporting PDSCH resources for UEs with reduced capabilities according to aspects of the present disclosure is shown. The operations of the method 2200 may be implemented by the base station 105 or components thereof as described herein. For example, the operations of the method 2200 may be implemented by the base station 105 or components thereof as described herein. Figures 15 to 18 In some examples, the base station may execute an instruction set to control the functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.
[0284] At 2205, the base station may receive a UE capability message from the UE, the UE capability message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth for the UE, a reduced number of antennas, or a combination thereof. The operations of 2205 may be performed according to the methods described herein. In some examples, aspects of the operations of 2205 may be performed as described with reference to Figures 15 to 18 The UE capability manager described in this document is used to perform the following operations:
[0285] At 2210, the base station may select a resource allocation scheme for a downlink grant for the UE based on the UE capability message and the supported bandwidth portion of the UE. The operations of 2210 may be performed according to the methods described herein. In some examples, aspects of the operations of 2210 may be as described with reference to Figures 15 to 18 Describes the resource allocation scheme manager to perform.
[0286] At 2215, the base station may send a downlink grant for downlink resources for data transmission to the UE according to the resource allocation scheme. The operations of 2215 may be performed according to the methods described herein. In some examples, aspects of the operations of 2215 may be as described with reference to Figures 15 to 18 Describes the authorization manager to perform.
[0287] At 2220, the base station may send a data transmission to the UE based on the downlink grant. The operations of 2220 may be performed according to the methods described herein. In some examples, aspects of the operations of 2220 may be as described with reference to Figures 15 to 18 Describes the data transfer manager to perform.
[0288] At 2225, the base station may send data transmissions on a supported BWP and using a low coding rate, the low coding rate being based on the UE type. The operations of 2225 may be performed according to the methods described herein. In some examples, aspects of the operations of 2225 may be as described with reference to Figures 15 to 18 Described in the BWP manager to perform.
[0289] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.
[0290] The technology described herein can be used in various wireless communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. A CDMA system can implement a radio technology such as CDMA 2000 or Universal Terrestrial Radio Access (UTRA). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. The IS-2000 version is commonly referred to as CDMA2000 1X or 1X. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO or High Rate Packet Data (HRPD). UTRA includes Wideband CDMA (W-CDMA) and other variants of CDMA. A TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM).
[0291] An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Professional are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Professional, NR, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Professional, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Professional, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-A Professional, or NR applications.
[0292] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with a service subscription with the network provider. Compared to a macro cell, a small cell may be associated with a lower power base station, and the small cell may operate in the same or different frequency band as the macro cell (e.g., licensed or unlicensed). According to various examples, small cells may include pico cells, femto cells, and micro cells. For example, a pico cell may cover a small geographic area and may allow unrestricted access by UEs with a service subscription with the network provider. A femto cell may also cover a small geographic area (e.g., a residence) and may provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). A base station for a macro cell may be referred to as a macro base station (e.g., a macro eNB or a macro gNB). A base station for a small cell may be referred to as a small base station (e.g., a small cell eNB or a small cell gNB), a pico base station (e.g., a pico eNB or a pico gNB), a femto base station (e.g., a femto eNB or a femto gNB), or a home base station (e.g., a home eNB or a home gNB). A base station may support one or more (e.g., two, three, four, etc.) cells and may also support communication using one or more component carriers.
[0293] The wireless communication systems described herein can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timing, and transmissions from different base stations can be approximately aligned in time. For asynchronous operation, base stations can have different frame timing, and transmissions from different base stations can be misaligned in time. The techniques described herein can be used for either synchronous or asynchronous operation.
[0294] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0295] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).
[0296] The functions described herein can be implemented with hardware, software executed by a processor, or any combination thereof. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc. If implemented with software executed by a processor, the functions can be stored on a computer-readable medium or sent therethrough as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, hard wiring, or any combination of these items. The features that implement the functions can also be physically located at various locations, including being distributed so that the various parts of the functions are implemented at different physical locations.
[0297] Computer readable medium includes non-transient computer storage medium and communication medium, and communication medium includes any medium that promotes the transmission of computer program from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general-purpose computer or special-purpose computer.By way of example and not limitation, non-transient computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device or can be used for carrying or storing desired program code unit and any other non-transient medium that can be accessed by general-purpose or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.In addition, any connection is suitably referred to as computer readable medium.For example, if software is to be sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.
[0298] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". As used herein, the term "and / or", when used in a list of two or more items, means that any one of the listed items can be adopted alone, or any combination of two or more of the listed items can be adopted. For example, if a composition is described as comprising elements A, B, and / or C, the composition may comprise: only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.
[0299] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between similar components. If only the first reference number is used in the specification, the description applies to any one of the similar components having the same first reference number, regardless of the second reference number or other subsequent reference numbers.
[0300] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that can be implemented or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.
[0301] The description herein is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the overall principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is intended to be used in the broadest sense consistent with the principles and novel features disclosed herein.
Claims
1. A method for wireless communication at a user equipment (UE), comprising: sending a UE capabilities message to a network device, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme based at least in part on the UE capability message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion of the UE; and In accordance with the downlink grant, a first transmission and a repeated transmission of the data transmission are received in a time slot of the supported bandwidth portion using a coding rate based at least in part on the UE type, wherein the data transmission is received according to the resource allocation scheme comprising interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported bandwidth portion, and the subset is based at least in part on the UE type, and wherein the first transmission and the repeated transmission are received based at least in part on a demodulation reference signal (DMRS) configuration associated with the time slot.
2. The method according to claim 1, wherein The coding rate based at least in part on the UE type includes a low coding rate below a threshold coding rate.
3. The method according to claim 2, further comprising: A scaling factor for a transport block size for the data transmission using the low coding rate is identified, the scaling factor being based at least in part on the UE type.
4. The method according to claim 2, further comprising: receiving a first DMRS transmission for the first transmission of the data transmission during a first time period of the first portion of the time slot; as well as A second DMRS transmission for the repeated transmission of the data transmission is received during a second time period of a second portion of the time slot, the first time period of the first portion of the time slot being different from the second time period of the second portion of the time slot.
5. The method according to claim 1, further comprising: identifying the DMRS configuration for receiving the first transmission and the repeated transmission in the time slot; as well as The data transmission is received based at least in part on the DMRS configuration.
6. The method according to claim 5, wherein: The DMRS configuration includes: A first DMRS transmission is received during a first portion of the time slot for the first transmission and a second DMRS transmission is received during a second portion of the time slot for the repeated transmission.
7. The method according to claim 6, wherein: The first DMRS transmission is received during an initial time period of the first portion of the time slot; and The second DMRS transmission is received during the initial time period of the second portion of the time slot.
8. The method according to claim 6, wherein: The first DMRS transmission is received during a first time period of the time slot that is used for the first portion of the first transmission; and The second DMRS transmission is received during a second time period of the second portion of the time slot for the repeated transmission, the first time period of the first portion of the time slot being different from the second time period of the second portion of the time slot.
9. The method according to claim 1, wherein The first transmission and the repeated transmission occur during the same symbol configuration or different symbol configurations in the time slot.
10. The method according to claim 1, further comprising: A first starting symbol for the first transmission and a second starting symbol for the repeated transmission are identified based at least in part on a downlink aggregation factor for intra-slot data repetition.
11. The method according to claim 1 , further comprising: A feedback signal for the data transmission is sent during a subsequent time slot having a time gap for processing based at least in part on the time slot in which the first transmission and the repeated transmission are received.
12. The method according to claim 1, further comprising: receiving one or more additional repetition transmissions of the data transmission in a second time slot occurring after the time slot in which the first transmission and the repetition transmission were received; and Based at least in part on the second time slot in which the one or more additional repetitive transmissions are received, a feedback signal is sent during a subsequent time slot having a time gap for processing.
13. The method according to claim 1, wherein Receiving the data transmission includes: receiving a first portion of the data transmission in a first time slot and on a first sub-band of the supported bandwidth portion; and A second portion of the data transmission is received in a second time slot on a second sub-band of the supported bandwidth portion, wherein the first sub-band is a different sub-band than the second sub-band.
14. The method according to claim 13, further comprising: The first portion of the data transmission and the second portion of the data transmission are received according to a same time domain configuration or a different time domain configuration between the first time slot and the second time slot.
15. The method according to claim 13, wherein The first subband and the second subband are in the same bandwidth portion or in different bandwidth portions.
16. The method according to claim 15, further comprising: determining that the first subband is in a first bandwidth portion and the second subband is in a second bandwidth portion different from the first bandwidth portion; as well as A retuning operation is performed during a retuning gap between receiving the first portion and receiving the second portion.
17. The method according to claim 16, wherein The retuning gap is a last portion in the first sub-band in the first bandwidth portion, or a first portion in the second sub-band in the second bandwidth portion, or a combination thereof.
18. The method according to claim 13, further comprising: The first portion in the first time slot and the second portion in the second time slot are received based at least in part on redundancy versions associated with the first and second portions of the data transmission.
19. The method of claim 1, further comprising: The data transmission is received based at least in part on a slot index, a repetition index, or a combination thereof.
20. A method for wireless communication at a network device, comprising: receiving a UE capabilities message from a user equipment (UE), the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; selecting a resource allocation scheme for a downlink grant for the UE based at least in part on the UE capability message and a supported bandwidth portion of the UE; sending the downlink grant for downlink resources for data transmission to the UE according to the resource allocation scheme; and and sending a first transmission and a repeated transmission of the data transmission to the UE in a time slot of the supported bandwidth portion in accordance with the downlink grant using a coding rate that is based at least in part on the UE type, wherein the data transmission is sent in accordance with the resource allocation scheme comprising interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported bandwidth portion, and the subset is based at least in part on the UE type, and wherein the first transmission and the repeated transmission are sent based at least in part on a demodulation reference signal (DMRS) configuration associated with the time slot.
21. The method according to claim 20, wherein The coding rate based at least in part on the UE type includes a low coding rate below a threshold coding rate.
22. The method according to claim 21, further comprising: A scaling factor of a transport block size to be used for the data transmission using the low coding rate is identified, the scaling factor being based at least in part on the UE type.
23. The method of claim 20, further comprising: identifying the DMRS configuration for sending the first transmission and the repeated transmission in the time slot; as well as The data transmission is sent based at least in part on the DMRS configuration.
24. The method according to claim 23, wherein The DMRS configuration includes: A first DMRS transmission is sent during a first portion of the time slot for the first transmission and a second DMRS transmission is sent during a second portion of the time slot for the repeated transmission.
25. The method of claim 24, wherein: The first DMRS transmission is sent during an initial time period of the first portion of the time slot for the first transmission; and The second DMRS transmission is sent during the initial time period of the second portion of the time slot for the repeated transmission.
26. An apparatus for wireless communication at a user equipment (UE), comprising: at least one processor; as well as a memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the UE to: sending a UE capabilities message to a network device, the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; receiving a downlink grant for downlink resources for data transmission according to a resource allocation scheme based at least in part on the UE capability message, wherein the resource allocation scheme is associated with the UE type and a supported bandwidth portion of the UE; and In accordance with the downlink grant, a first transmission and a repeated transmission of the data transmission are received in a time slot of the supported bandwidth portion using a coding rate based at least in part on the UE type, wherein the data transmission is received according to the resource allocation scheme comprising interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported bandwidth portion, and the subset is based at least in part on the UE type, and wherein the first transmission and the repeated transmission are received based at least in part on a demodulation reference signal (DMRS) configuration associated with the time slot.
27. An apparatus for wireless communication at a network device, comprising: at least one processor; as well as A memory coupled to the at least one processor, the memory storing instructions executable by the at least one processor to cause the network device to: receiving a UE capabilities message from a user equipment (UE), the UE capabilities message including an indication of a UE type, wherein the UE type is associated with at least one of a reduced bandwidth, a reduced number of antennas, or a combination thereof for the UE; selecting a resource allocation scheme for a downlink grant for the UE based at least in part on the UE capability message and a supported bandwidth portion of the UE; sending the downlink grant for downlink resources for data transmission to the UE according to the resource allocation scheme; and and sending a first transmission and a repeated transmission of the data transmission to the UE in a time slot of the supported bandwidth portion in accordance with the downlink grant using a coding rate that is based at least in part on the UE type, wherein the data transmission is sent in accordance with the resource allocation scheme comprising interleaved and non-contiguous resource blocks distributed across a subset of available subbands in the supported bandwidth portion, and the subset is based at least in part on the UE type, and wherein the first transmission and the repeated transmission are sent based at least in part on a demodulation reference signal (DMRS) configuration associated with the time slot.
Citation Information
Patent Citations
Mobile communication device and method for allocating resources outside of a virtual carrier based on UE capabilities
US20150365945A1