WO2020118632A1 - Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport - Google Patents

Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport Download PDF

Info

Publication number
WO2020118632A1
WO2020118632A1 PCT/CN2018/120924 CN2018120924W WO2020118632A1 WO 2020118632 A1 WO2020118632 A1 WO 2020118632A1 CN 2018120924 W CN2018120924 W CN 2018120924W WO 2020118632 A1 WO2020118632 A1 WO 2020118632A1
Authority
WO
WIPO (PCT)
Prior art keywords
transport blocks
scheduled
downlink control
scheduling
dci
Prior art date
Application number
PCT/CN2018/120924
Other languages
English (en)
Inventor
Chao Wei
Alberto Rico Alvarino
Ayan SENGUPTA
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2018/120924 priority Critical patent/WO2020118632A1/fr
Publication of WO2020118632A1 publication Critical patent/WO2020118632A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals

Definitions

  • the following relates generally to wireless communications, and more specifically to downlink control information (DCI) design for scheduling of multiple transport blocks, for example, in a narrowband wireless communications system (e.g., a machine-type communication (MTC) system, a narrowband Internet-of-Things (NB-IoT) system, etc. ) .
  • DCI downlink control information
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems.
  • 4G systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems
  • 5G systems which may be referred to as New Radio (NR) systems.
  • a wireless multiple-access communications system may include a number of base stations or network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • a base station may schedule downlink or uplink transmissions for a UE using DCI.
  • DCI transmissions may be used to dynamically schedule downlink or uplink transmissions, or may be used to trigger persistent scheduling, where periodic resource allocations are scheduled.
  • Dynamic scheduling may be used to schedule one or more transport blocks in a single transmission time interval (TTI) or may schedule multiple transport blocks across multiple TTIs. Scheduling multiple transport blocks across multiple TTIs with one DCI transmission may reduce DCI overhead by reducing the number of DCI transmissions. However, scheduling of multiple transport blocks across multiple TTIs may introduce a large amount of overhead in the single DCI transmission, reducing the benefit of dynamically scheduling multiple transport blocks.
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support downlink control information (DCI) design for scheduling of multiple transport blocks.
  • DCI downlink control information
  • the described techniques provide for a common DCI payload size configured to support scheduling of a number of transport blocks (e.g., one, or up to a maximum number) with conditional state encoding.
  • a base station may determine a number of transport blocks to schedule and may determine whether to apply a scheduling limitation to information used to schedule the transport blocks based on the number of transport blocks.
  • the base station may then encode the information using conditionally encoded DCI fields based on the number of transport blocks and the scheduling limitation.
  • the information may include a flag indicating whether multiple transport blocks are scheduled.
  • the base station may transmit the encoded DCI and a user equipment (UE) may decode the DCI according to the flag and conditionally encoded DCI fields to determine the information used to schedule the transport blocks.
  • UE user equipment
  • a method for wireless communications may include determining a number of transport blocks to schedule within a DCI transmission, determining whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encoding the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmitting the encoded information in the DCI transmission.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to determine a number of transport blocks to schedule within a DCI transmission, determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmit the encoded information in the DCI transmission.
  • the apparatus may include means for determining a number of transport blocks to schedule within a DCI transmission, determining whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encoding the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmitting the encoded information in the DCI transmission.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to determine a number of transport blocks to schedule within a DCI transmission, determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmit the encoded information in the DCI transmission.
  • a zero codepoint for the flag indicates that one transport block is scheduled within the DCI transmission and a non-zero codepoint for the flag indicates that multiple transport blocks are scheduled within the DCI transmission.
  • the number of transport blocks to schedule may be greater than one.
  • determining whether to apply the scheduling limitation may include operations, features, means, or instructions for limiting a set of subcarrier resources for subcarrier resource assignment for scheduling multiple transport blocks within the DCI transmission based on the number of transport blocks to schedule being greater than one and selecting a subcarrier resource for the multiple transport blocks from the limited set of subcarrier resources, where the information includes the selected subcarrier resource.
  • the number of transport blocks to schedule may be greater than one.
  • the encoding may include operations, features, means, or instructions for indicating a new data indicator (NDI) value for one of the transport blocks using a first bit position in the information, where the first bit position may be associated with a hybrid automatic repeat request (HARQ) process number when the number of transport blocks to schedule is one, and indicating a redundancy version (RV) for one of the transport blocks using a second bit position in the information, where the second bit position may be associated with a subcarrier resource assignment when the number of transport blocks to schedule is one.
  • NDI new data indicator
  • HARQ hybrid automatic repeat request
  • RV redundancy version
  • the number of transport blocks to schedule may be greater than one and determining whether to apply the scheduling limitation may include operations, features, means, or instructions for limiting each transport block scheduled within the DCI transmission to a common NDI value and a common RV value.
  • the number of transport blocks to schedule may be greater than one, and encoding the information may include operations, features, means, or instructions for jointly encoding at least a portion of the information for the DCI transmission based on the number of transport blocks to schedule being greater than one.
  • a bit position of at least the portion of the information that is jointly encoded may be associated with a modulation and coding scheme (MCS) when the number of transport blocks to schedule is one.
  • MCS modulation and coding scheme
  • jointly encoding at least the portion of the information may include operations, features, means, or instructions for jointly encoding a non-zero codepoint value for the flag with at least the portion of the information.
  • jointly encoding at least the portion of the information may include operations, features, means, or instructions for jointly encoding an MCS, an RV, a repetition number, or some combination thereof for scheduling multiple transport blocks within the DCI transmission based on the number of transport blocks to schedule being greater than one.
  • determining whether to apply the scheduling limitation may include operations, features, means, or instructions for selecting the repetition number for scheduling the multiple transport blocks, limiting a number of MCSs, a number of RVs, or both based on the repetition number, and selecting the MCS from the limited number of MCSs, the RV from the limited number of RVs, or both for scheduling the multiple transport blocks.
  • jointly encoding at least the portion of the information may include operations, features, means, or instructions for jointly encoding the number of transport blocks to schedule and respective HARQ process numbers for each transport block.
  • jointly encoding the number of transport blocks to schedule and the respective HARQ process numbers for each transport block may include operations, features, means, or instructions for determining a combination index based on the respective HARQ process number for each transport block, a table stored in a memory, an equation stored in the memory, or a combination thereof, where the combination index indicates the number of transport blocks to schedule and the respective HARQ process number for each transport block, where the information includes the combination index.
  • the respective HARQ process numbers for the transport blocks may be indicated sequentially in an increasing order.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting downlink information in one or more transport blocks scheduled within the DCI transmission.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a payload size for the information for the DCI transmission, where the payload size may be the same for scheduling different numbers of transport blocks within the DCI transmission.
  • the number of transport blocks to schedule may be greater than one, and each transport block scheduled within the DCI transmission corresponds to a different transmission time interval (TTI) . In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the number of transport blocks to schedule may be greater than one, and each transport block scheduled within the DCI transmission corresponds to a different HARQ process.
  • TTI transmission time interval
  • the number of transport blocks to schedule may be greater than one, and each transport block scheduled within the DCI transmission corresponds to a different HARQ process.
  • a method of wireless communications may include receiving encoded information in a DCI transmission, decoding, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decoding, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identifying one or more scheduled transport blocks based on the transport block scheduling information.
  • the apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory.
  • the instructions may be executable by the processor to cause the apparatus to receive encoded information in a DCI transmission, decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the apparatus may include means for receiving encoded information in a DCI transmission, decoding, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decoding, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identifying one or more scheduled transport blocks based on the transport block scheduling information.
  • a non-transitory computer-readable medium storing code for wireless communications is described.
  • the code may include instructions executable by a processor to receive encoded information in a DCI transmission, decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identify one or more scheduled transport blocks based on the transport block scheduling information.
  • a zero codepoint for the flag indicates that one transport block is scheduled within the DCI transmission and a non-zero codepoint for the flag indicates that multiple transport blocks are scheduled within the DCI transmission.
  • each transport block scheduled within the DCI transmission corresponds to a common NDI value and a common RV value.
  • multiple transport blocks may be scheduled within the DCI transmission, where decoding the transport block scheduling information may include operations, features, means, or instructions for identifying an NDI value for one of the one or more scheduled transport blocks using a first bit position in the transport block scheduling information, where the first bit position may be associated with a HARQ process number when multiple transport blocks are not scheduled, and identifying an RV for one of the one or more scheduled transport blocks using a second bit position in the transport block scheduling information, where the second bit position may be associated with a subcarrier resource assignment when multiple transport blocks are not scheduled (e.g., when a single transport block is scheduled) .
  • multiple transport blocks may be scheduled within the DCI transmission, where decoding the transport block scheduling information may include operations, features, means, or instructions for jointly decoding at least a portion of the transport block scheduling information based on multiple transport blocks being scheduled within the DCI transmission.
  • a bit position of the transport block scheduling information that may be jointly decoded may be associated with an MCS when multiple transport blocks are not scheduled.
  • decoding the flag may include operations, features, means, or instructions for jointly decoding a non-zero codepoint value for the flag and at least the portion of the transport block scheduling information.
  • jointly decoding at least the portion of the transport block scheduling information may include operations, features, means, or instructions for jointly decoding an MCS, an RV, a repetition number, or some combination thereof for the multiple transport blocks based on the multiple transport blocks being scheduled within the DCI transmission.
  • jointly decoding the MCS, the RV, and the repetition number for the multiple transport blocks further may include operations, features, means, or instructions for determining the repetition number, and determining a number of bits indicating the MCS, a number of bits indicating the RV, or both based on the determined repetition number.
  • jointly decoding at least the portion of the transport block scheduling information may include operations, features, means, or instructions for jointly decoding a number of scheduled transport blocks and a respective HARQ process number for each of the multiple transport blocks.
  • jointly decoding the number of scheduled transport blocks and the respective HARQ process numbers for each of the multiple transport blocks may include operations, features, means, or instructions for decoding a combination index based on a table stored in a memory, an equation stored in the memory, or a combination thereof, where the combination index indicates the number of scheduled transport blocks and the respective HARQ process numbers for each of the multiple transport blocks.
  • the respective HARQ process numbers for the multiple transport blocks may be indicated sequentially in an increasing order.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving downlink information in the identified one or more transport blocks.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a payload size corresponding to the encoded information, where the payload size may be the same for different numbers of transport blocks scheduled within the DCI transmission.
  • multiple transport blocks are scheduled within the DCI transmission and each transport block scheduled within the DCI transmission corresponds to a different TTI. In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, multiple transport blocks are scheduled within the DCI transmission and each transport block scheduled within the DCI transmission corresponds to a different HARQ process.
  • FIGs. 1 and 2 illustrate examples of wireless communications systems that support downlink control information (DCI) design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • DCI downlink control information
  • FIGs. 3 through 5 illustrate examples of DCI configurations for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIG. 6 illustrates an example of a process flow that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 7 and 8 show block diagrams of devices that support DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIG. 9 shows a block diagram of a DCI manager that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIG. 10 shows a diagram of a system including a device that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 11 and 12 show block diagrams of devices that support DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIG. 13 shows a block diagram of a DCI manager that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIG. 14 shows a diagram of a system including a device that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 15 through 18 show flowcharts illustrating methods that support DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • a base station may schedule downlink or uplink transmissions for a UE using downlink control information (DCI) .
  • DCI downlink control information
  • a downlink or uplink transmission may include one or more transport blocks, where a transport block is associated with a process identifier for error control (e.g., hybrid automatic repeat request (HARQ) number) .
  • DCI transmissions may be used to dynamically schedule downlink or uplink transmissions, or may be used to trigger persistent scheduling, where periodic resource allocations are scheduled.
  • Dynamic scheduling may be used to schedule one or more transport blocks in a single transmission time interval (TTI) or may schedule multiple transport blocks across multiple TTIs.
  • TTI transmission time interval
  • Persistent scheduling is used to schedule first transmissions for one or more transport blocks in the periodically allocated TTIs, and the allocations for each of the periodic TTIs are associated with the same transport blocks.
  • Semi-persistent scheduling may refer to scheduling initial transmissions for one or more transport blocks (i.e., not retransmissions) using persistent scheduling, and scheduling retransmissions for the transport blocks using dynamic scheduling.
  • Scheduling multiple transport blocks across multiple TTIs with one DCI transmission may reduce DCI overhead by reducing the number of DCI transmissions.
  • scheduling of multiple transport blocks across multiple TTIs may introduce a large amount of overhead in the single DCI transmission if the fields for each transport block are individually encoded, reducing the benefit of dynamically scheduling multiple transport blocks.
  • each transport block may be associated with a different resource assignment, subcarrier indication, HARQ process number, modulation and coding scheme (MCS) , new data indicator (NDI) , redundancy version (RV) , or repetition number.
  • MCS modulation and coding scheme
  • NDI new data indicator
  • RV redundancy version
  • using the same resource assignment or subcarrier indication across all the transport blocks may limit the DCI overhead.
  • the remaining fields may still require a large amount of overhead.
  • NDI values one bit
  • RV values two bits
  • 4N bits For example, using bitmaps to indicate the presence or absence of every HARQ process, NDI values (one bit) , and RV values (two bits) may require 4N bits.
  • Using individual MCS values would require typically five (5) bits per transport block, while using a common MCS value would require five (5) bits in addition to the transport block specific information.
  • Joint encoding may be used to reduce the number of bits in the DCI by eliminating redundant combinations.
  • the NDI and RV may be jointly coded for each transport block, resulting in nine (9) valid combinations (one (1) from when the HARQ process is not scheduled, and eight (8) from when the process is scheduled) .
  • RV is not present, there are three (3) valid combinations for the presence or absence of a HARQ process number and NDI (one (1) from when the HARQ process is not scheduled and two (2) from when the process is scheduled with NDI equal to zero (0) or one (1) ) .
  • Joint encoding for N HARQ processes can thus save for DCI with a two (2) bit RV field per HARQ process number or for DCI with a zero-bit RV field per HARQ process number.
  • applying scheduling restrictions can be used to limit the number of bits required for the DCI. For example, restricting to a common NDI and RV for all the scheduled transport blocks saves a significant number of bits in the DCI.
  • Using bitmaps to indicate the presence or absence of each HARQ process of a maximum N HARQ processes may result in an increase of N-log 2 N bits to the DCI payload (e.g., even with a common NDI and RV) .
  • the DCI size may be based on a maximum number of HARQ processes and does not adapt based on the number of scheduled transport blocks (which can be smaller than the maximum number of HARQ processes) , and thus a single DCI format may only apply to limited types of scheduling (e.g., transmissions, retransmissions, a single transport block, scheduling of multiple transport blocks) .
  • the following table shows a comparison of individual encoding and joint encoding.
  • the bits saved by joint encoding is not significant, and the complexity of joint encoding may not be warranted.
  • a recursive approach may be required for encoding or decoding of the DCI.
  • a multiple transport block scheduling flag may be used, which may signal whether a single transport block is scheduled or multiple transport blocks are scheduled.
  • the DCI may schedule a single transport block, using individual coding for example for the HARQ process number, NDI, and RV fields.
  • the flag has a second value (e.g., one (1) )
  • the DCI may schedule multiple transport blocks, with a scheduling limitation applied to maintain a consistent number of bits for the DCI for a single transport block or multiple transport blocks.
  • the scheduling information for the multiple transport blocks may be jointly coded.
  • the scheduling limitation may be, for example, limiting the resource assignment, number of MCS states, number of RV states, number of repetition number states. There saved bit (s) may be used for the flag or jointly encoded states. Additionally or alternatively, a common NDI or RV may be used for all the scheduled transport blocks.
  • aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects of the disclosure are described with reference to DCI configurations and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to DCI design for scheduling of multiple transport blocks.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the wireless communications system 100 includes base stations 105, UEs 115, and a core network 130.
  • the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • NR New Radio
  • wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.
  • ultra-reliable e.g., mission critical
  • Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas.
  • Base stations 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or some other suitable terminology.
  • Wireless communications system 100 may include base stations 105 of different types (e.g., macro or small cell base stations) .
  • the UEs 115 described herein may be able to communicate with various types of base stations 105 and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like.
  • Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with various UEs 115 is supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via communication links 125, and communication links 125 between a base station 105 and a UE 115 may utilize one or more carriers. Communication links 125 shown in wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions from a base station 105 to a UE 115. Downlink transmissions may also be called forward link transmissions while uplink transmissions may also be called reverse link transmissions.
  • the geographic coverage area 110 for a base station 105 may be divided into sectors making up a portion of the geographic coverage area 110, and each sector may be associated with a cell.
  • each base station 105 may provide communication coverage for a macro cell, a small cell, a hot spot, or other types of cells, or various combinations thereof.
  • a base station 105 may be movable and therefore provide communication coverage for a moving geographic coverage area 110.
  • different geographic coverage areas 110 associated with different technologies may overlap, and overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or by different base stations 105.
  • the wireless communications system 100 may 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.
  • the term “cell” refers to a logical communication entity used for communication with a base station 105 (e.g., over a carrier) , and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) operating via the same or a different carrier.
  • a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine-type communication (MTC) , narrowband Internet-of-Things (NB-IoT) , enhanced mobile broadband (eMBB) , or others) that may provide access for different types of devices.
  • MTC machine-type communication
  • NB-IoT narrowband Internet-of-Things
  • eMBB enhanced mobile broadband
  • the term “cell” may refer to a portion of a geographic coverage area 110 (e.g., a sector) over which the logical entity operates.
  • UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client.
  • a UE 115 may 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.
  • PDA personal digital assistant
  • a UE 115 may also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, or the like, which may be implemented in various articles such as appliances, vehicles, meters, or the like.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC massive machine type communications
  • Some UEs 115 may be low cost or low complexity devices, and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) .
  • M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station 105 without human intervention.
  • M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application.
  • Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
  • Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception simultaneously) . In some examples half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for UEs 115 include entering a power saving “deep sleep” mode when not engaging in active communications, or operating over a limited bandwidth (e.g., according to narrowband communications) . In some cases, UEs 115 may be designed to support critical functions (e.g., mission critical functions) , and a wireless communications system 100 may be configured to provide ultra-reliable communications for these functions.
  • critical functions e.g., mission critical functions
  • a UE 115 may also be able to communicate directly with other UEs 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol) .
  • P2P peer-to-peer
  • D2D device-to-device
  • One or more of a group of UEs 115 utilizing D2D communications may be within the geographic coverage area 110 of a base station 105.
  • Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105, or be otherwise unable to receive transmissions from a base station 105.
  • groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1 ⁇ M) system in which each UE 115 transmits to every other UE 115 in the group.
  • a base station 105 facilitates the scheduling of resources for D2D communications.
  • D2D communications are carried out between UEs 115 without the involvement of a base
  • Base stations 105 may communicate with the core network 130 and with one another.
  • base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., via an S1, N2, N3, or other interface) .
  • Base stations 105 may communicate with one another over backhaul links 134 (e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) .
  • 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 transferred through the S-GW, which itself may be connected to the P-GW.
  • the P-GW may provide IP address allocation as well as other functions.
  • the P-GW may be connected to the network operators IP services.
  • the operators IP services may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched (PS) Stream
  • At least some of the network devices may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC) .
  • Each access network entity may communicate with UEs 115 through a number of other access network transmission entities, which may be referred to as a radio head, a smart radio head, or a transmission/reception point (TRP) .
  • TRP transmission/reception point
  • 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., a base station 105) .
  • Wireless communications system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) .
  • the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, since the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features. However, the waves may penetrate structures sufficiently for a macro cell to provide service to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter range (e.g., less than 100 km) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
  • HF high frequency
  • VHF very high frequency
  • Wireless communications system 100 may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band.
  • SHF region includes bands such as the 5 GHz industrial, scientific, and medical (ISM) bands, which may be used opportunistically by devices that may be capable of tolerating interference from other users.
  • ISM bands 5 GHz industrial, scientific, and medical bands
  • Wireless communications system 100 may also operate in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band.
  • EHF extremely high frequency
  • wireless communications system 100 may support millimeter wave (mmW) communications between UEs 115 and base stations 105, and EHF antennas of the respective devices may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE 115.
  • mmW millimeter wave
  • the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. Techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
  • wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz ISM band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz ISM band.
  • wireless devices such as base stations 105 and UEs 115 may employ listen-before-talk (LBT) procedures to ensure a frequency channel is clear before transmitting data.
  • LBT listen-before-talk
  • operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating in a licensed band (e.g., LAA) .
  • Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these.
  • Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD) , time division duplexing (TDD) , or a combination of both.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • base station 105 or 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) communications, or beamforming.
  • wireless communications system 100 may use a transmission scheme between a transmitting device (e.g., a base station 105) and a receiving device (e.g., a UE 115) , where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas.
  • MIMO communications may employ multipath signal propagation to increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing.
  • the multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device 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 used for channel measurement and reporting.
  • MIMO techniques include single-user MIMO (SU-MIMO) where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) where multiple spatial layers are transmitted to multiple devices.
  • SU-MIMO single-user MIMO
  • MU-MIMO multiple-user MIMO
  • Beamforming which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or steer an antenna beam (e.g., a transmit beam or receive beam) along a spatial path between the transmitting device and the receiving device.
  • Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference.
  • the adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying certain amplitude and phase offsets to signals carried via each of the antenna elements associated with the device.
  • the adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
  • a base station 105 may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115. For instance, some signals (e.g. synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station 105 multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by the base station 105 or a receiving device, such as a UE 115) a beam direction for subsequent transmission and/or reception by the base station 105.
  • some signals e.g. synchronization signals, reference signals, beam selection signals, or other control signals
  • Transmissions in different beam directions may be used to identify (e.g., by the base station 105 or a receiving device, such as a UE 115) a beam direction for subsequent transmission and/or reception by the base station 105.
  • Some signals may be transmitted by a base station 105 in a single beam direction (e.g., a direction associated with the receiving device, such as a UE 115) .
  • the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions.
  • a UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE 115 may report to the base station 105 an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality.
  • a UE 115 may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) , or transmitting a signal in a single direction (e.g., for transmitting data to a receiving device) .
  • a receiving device may try multiple receive beams when receiving various signals from the base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals.
  • a 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 receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at a plurality of antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive beams or receive directions.
  • a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal) .
  • the single receive beam may be aligned in a beam direction determined based at least in part on listening according to different receive beam directions (e.g., a beam direction determined to have a 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) .
  • the antennas of a base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operations, or transmit or receive beamforming.
  • one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower.
  • antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations.
  • a base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use to support beamforming of communications with a UE 115.
  • a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.
  • wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack.
  • PDCP Packet Data Convergence Protocol
  • a Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels.
  • RLC Radio Link Control
  • a Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels.
  • the MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmission at the MAC layer to improve link efficiency.
  • HARQ hybrid automatic repeat request
  • the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a base station 105 or core network 130 supporting radio bearers for user plane data.
  • RRC Radio Resource Control
  • transport channels may be mapped to physical channels.
  • UEs 115 and base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • HARQ feedback is one technique of increasing the likelihood that data is received correctly over a 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) ) .
  • FEC forward error correction
  • ARQ automatic repeat request
  • HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., signal-to-noise conditions) .
  • a wireless device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
  • the radio frames may be identified by a system frame number (SFN) ranging from 0 to 1023.
  • SFN system frame number
  • Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms.
  • a subframe may be further divided into 2 slots each having a duration of 0.5 ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods.
  • a subframe may be the smallest scheduling unit of the wireless communications system 100, and may be referred to as a transmission time interval (TTI) .
  • TTI transmission time interval
  • a smallest scheduling unit of the wireless communications system 100 may be shorter than a subframe or may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) or in selected component carriers using sTTIs) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols.
  • a symbol of a mini-slot or a mini-slot may be the smallest unit of scheduling.
  • Each symbol may vary in duration depending on the subcarrier spacing or frequency band of operation, for example.
  • some wireless communications systems may implement slot aggregation in which multiple slots or mini-slots are aggregated together and used for communication between a UE 115 and a base station 105.
  • carrier refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over a communication link 125.
  • a carrier of a communication link 125 may include a portion of a radio frequency spectrum band that is operated according to physical layer channels 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 pre-defined frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN) ) , and may be positioned according to a channel raster for discovery by UEs 115.
  • E-UTRA evolved universal mobile telecommunication system terrestrial radio access
  • E-UTRA absolute radio frequency channel number
  • Carriers may be downlink or uplink (e.g., in an FDD mode) , or be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
  • signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) .
  • MCM multi-carrier modulation
  • OFDM orthogonal frequency division multiplexing
  • DFT-S-OFDM discrete Fourier transform spread OFDM
  • the organizational structure of the carriers may be different for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • communications over a carrier may be organized according to TTIs or slots, each of which may include user data as well as control information or signaling to support decoding the user data.
  • a carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc. ) and control signaling that coordinates operation for the carrier.
  • acquisition signaling e.g., synchronization signals or system information, etc.
  • control signaling that coordinates operation for the carrier.
  • a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.
  • Physical channels may be multiplexed on a carrier according to various techniques.
  • a physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • control information transmitted in a physical control channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces) .
  • a carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100.
  • the carrier bandwidth may be one of a number of predetermined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) .
  • each served UE 115 may be configured for operating over portions or all of the carrier bandwidth.
  • some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a predefined portion or range (e.g., set of subcarriers or RBs) within a carrier (e.g., “in-band” deployment of a narrowband protocol type) .
  • a narrowband protocol type that is associated with a predefined portion or range (e.g., set of subcarriers or RBs) within a carrier (e.g., “in-band” deployment of a narrowband protocol type) .
  • a resource element may span one symbol period (e.g., a 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) .
  • the more resource elements that a UE 115 receives and the higher the order of the modulation scheme the higher the data rate may be for the UE 115.
  • a wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers) , and the use of multiple spatial layers may further increase the data rate for communications with a UE 115.
  • a spatial resource e.g., spatial layers
  • Devices of the wireless communications system 100 may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths.
  • the wireless communications system 100 may include base stations 105 and/or UEs 115 that support simultaneous communications via carriers associated with more than one different carrier bandwidth.
  • Wireless communications system 100 may support communication with a UE 115 on multiple cells or carriers, a feature which may be referred to as carrier aggregation or multi-carrier operation.
  • a UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration.
  • Carrier aggregation may be used with both FDD and TDD component carriers.
  • wireless communications system 100 may utilize enhanced component carriers (eCCs) .
  • eCC may be characterized by one or more features including wider carrier or frequency channel bandwidth, shorter symbol duration, shorter TTI duration, or modified control channel configuration.
  • an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link) .
  • 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 wide carrier bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to conserve power) .
  • an eCC may utilize a different symbol duration than other component carriers, which may include use of a reduced symbol duration as compared with symbol durations of the other component carriers.
  • a shorter symbol duration may be associated with increased spacing between adjacent subcarriers.
  • a device such as a UE 115 or base station 105, utilizing eCCs may transmit wideband signals (e.g., according to frequency channel or carrier bandwidths of 20, 40, 60, 80 MHz, etc. ) at reduced symbol durations (e.g., 16.67 microseconds) .
  • a TTI in eCC may span one or multiple symbol periods. In some cases, the TTI duration (that is, the number of symbol periods in a TTI) may be variable.
  • Wireless communications system 100 may be an NR system that may utilize any combination of licensed, shared, and unlicensed spectrum bands, among others.
  • the flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums.
  • NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across the frequency domain) and horizontal (e.g., across the time domain) sharing of resources.
  • control information may include a multiple transport block scheduling flag, which may signal whether a single transport block is scheduled or multiple transport blocks are scheduled.
  • the flag has a first value (e.g., a zero codepoint, where each bit in the flag is a zero (0) bit)
  • the DCI may schedule a single transport block, using individual coding for example for the HARQ process number, NDI, and RV fields.
  • the DCI may schedule multiple transport blocks, with a scheduling limitation applied to maintain a consistent number of bits for the DCI for a single transport block or multiple transport blocks.
  • the scheduling information for the multiple transport blocks may be jointly coded.
  • the scheduling limitation may be, for example, limiting the resource assignment, number of MCS states, number of RV states, number of repetition number states, etc.
  • the saved bit (s) may be used for the flag or jointly encoded states. Additionally or alternatively, a common NDI or RV may be used for all the scheduled transport blocks within a single DCI.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the wireless communications system 200 may include base station 105-a and UE 115-a, which may be examples of the corresponding devices described with reference to FIG. 1.
  • Base station 105-a may provide network coverage for geographic coverage area 110-a.
  • base station 105-a may use one DCI (e.g., in a single DCI transmission 210 on a downlink channel 205) to schedule downlink or uplink transmissions in multiple transport blocks 215 for UE 115-a.
  • Scheduling multiple transport blocks 215 in a single DCI transmission 210 may reduce the overhead on the control channel that the DCI is transmitted over.
  • This control channel may be an example of a physical downlink control channel (PDCCH) , an MTC PDCCH (MPDCCH) , a narrowband PDCCH (NPDCCH) , or some similar channel.
  • Base station 105-a may implement one or more DCI configurations or techniques for reducing the DCI transmission 210 payload for scheduling multiple transport blocks 215, reducing the overhead on the control channel.
  • Some wireless communications systems 200 support multi-transport block dynamic scheduling in a DCI transmission 210. These multiple transport blocks 215 may be scheduled in different TTIs (e.g., frames, subframes, slots, mini-slots, symbols, etc. ) , and each transport block 215 may correspond to a different HARQ process. In some cases, these TTIs may be contiguous, while in other cases the TTIs for the transport blocks 215 may be non-contiguous. Multi-transport block scheduling in the DCI may support efficient control channel usage for a downlink channel 205.
  • TTIs e.g., frames, subframes, slots, mini-slots, symbols, etc.
  • scheduling multiple transport blocks 215 in a single DCI transmission 210 may introduce a number of new DCI fields to indicate scheduling information (e.g., DCI fields to indicate the number of scheduled transport blocks, transport block-specific parameters, etc. ) . If the DCI size for scheduling multiple transport blocks 215 is too large
  • multi-transport block scheduling may result in significant control channel resource usage. Additionally or alternatively, if multiple DCI transmission 210 repetitions are needed for reliable decoding of the DCI at UE 115-a, the control channel overhead may increase rather than decrease, reducing or negating the gains of scheduling multiple transport blocks 215 in a single DCI transmission 210.
  • Scheduling multiple transport blocks 215 in a single DCI transmission may impact a number of DCI fields. While a resource assignment may be the same for all transport blocks 215 scheduled in a DCI, HARQ process numbers and NDIs may be defined on a per transport block 215 basis. As such, scheduling multiple transport blocks 215 may involve indicating multiple values for these parameters. Additionally, MCS and RV values may be common for initial transport block 215 scheduling but may be different for certain transport block 215 re-transmissions. The impact of scheduling multi-transport blocks on the DCI fields may be common across uplink and downlink grants for multiple wireless communications systems
  • the following tables indicate the impact of scheduling multiple transport blocks 215 on different DCI fields, where the “legacy” DCI formats described correspond to conventional systems supporting single transport block scheduling per DCI:
  • CE Mode B for eMTC operation may not include an RV DCI field, as the RV may have a common value (e.g., zero (0) ) for both initial transmissions and re-transmissions.
  • RV cycling may be implemented in the uplink for CE Mode B.
  • a DCI format for downlink NB-IoT may not include an RV DCI field.
  • a conventional system may support individual encoding of HARQ process ID, NDI, and RV values for multiple transport blocks 215 scheduled in a DCI transmission 210.
  • a base station may use a HARQ process bitmap to indicate the presence or absence of each HARQ process (e.g., from 1 to N, where N corresponds to the maximum number of possible HARQ processes supported by a single DCI) , where each bit in the bitmap corresponds to one HARQ process.
  • this HARQ process bitmap may use N bits to indicate the scheduled HARQ processes.
  • the base station may additionally use an N-bit NDI bitmap with an NDI indicator for each HARQ process, where the NDI indicator toggles upon a new transport block 215 being scheduled in the corresponding HARQ process, and a 2N-bit RV index bitmap, where two bits are used to indicate the RV of a transport block 215 being scheduled for each HARQ process.
  • the base station 105 may further indicate an MCS value (e.g., a common MCS across the transport blocks 215 scheduled in a same DCI) using a set of bits (e.g., four (4) or five (5) bits) .
  • the DCI payload may correspond to 4N bits (or 2N bits if no RV field is present) .
  • a conventional system may support joint encoding of HARQ process IDs and NDIs or HARQ process IDs, NDIs, and RV Indices.
  • a base station 105 may eliminate several redundant combinations of these fields from the DCI using the joint encoding. For example, if a HARQ process is not scheduled, the NDI and RV index fields corresponding to this HARQ process are redundant and can be removed from the DCI payload.
  • the base station 105 may indicate one of nine possible jointly valid combinations (e.g., one where the HARQ process is not scheduled and eight corresponding to the different combinations of NDIs (e.g., one bit) and RV indices (e.g., two bits) for a scheduled HARQ process) . Furthermore, if an RV field is not present in the DCI, the base station may indicate one of three possible jointly valid combinations (e.g., one where the HARQ process is not scheduled and two for the two possible values of the NDI bit when the HARQ process is scheduled) .
  • the DCI payload may correspond to bits (or if no RV field is present) . Accordingly, joint encoding may result in a lower DCI payload than individual encoding.
  • joint encoding may not have any significant reduction in the DCI payload while increasing the decoding complexity for the DCI (e.g., as a UE may need to perform a recursive decoding process on the jointly encoded DCI to loop over all the HARQ processes in order to determine the values of the individual DCI fields) .
  • a conventional system may restrict all transport blocks 215 scheduled in a same DCI to a common NDI and a common RV, reducing the DCI payload by simplifying the number of possible combinations.
  • a base station may include an N-bit HARQ process bitmap in DCI to indicate scheduling for transport blocks 215, resulting in an increase of N-log 2 N bits to the DCI payload.
  • Such a conventional system may schedule initial transmissions of multiple transport blocks within one DCI (e.g., with a common NDI of 0) and may schedule re-transmissions of multiple transport blocks in another DCI (e.g., with a common NDI of 1) .
  • the base station may not adapt the DCI size based on a configured maximum number of scheduled transport blocks 215 for a single DCI. For example, the base station may use N bits in the DCI for N HARQ processes even if the maximum number of scheduled transport blocks 215 within one DCI is smaller than N.
  • the HARQ process bitmap may be extended from a HARQ process ID field to support backwards compatibility with a DCI scheduling a single transport block 215.
  • wireless communications system 200 may support a multi-transport block flag for indicating single transport block or multi-transport block scheduling in a DCI transmission 210.
  • the multi-transport block flag may be a single bit or a bit field, where one value for the multi-transport block flag (e.g., zero codepoint) indicates that a single transport block 215 is scheduled in the DCI transmission 210.
  • Other values for the multi-transport block flag e.g., any non-zero codepoint
  • base station 105-a may support full combinations of HARQ process IDs, NDIs, and RVs for the two HARQ processes.
  • base station 105-a may either limit MCS or resource assignment selection for the transport block scheduling to save one bit from one of these indications.
  • Base station 105-a may use this one bit with three bits corresponding to single transport block scheduling HARQ ID, NDI, and RV fields to indicate multi-transport block scheduling (e.g., HARQ ID, NDI and RV fields) using four bits.
  • base station 105-a may be pre-configured to limit either the MCS or the resource assignment selection. In other cases, base station 105-a may dynamically or semi-statically determine to limit one of these fields according to a logical rule (e.g., where UE 115-a also follows the logical rule to correctly decode the resulting DCI transmission 210) .
  • a logical rule e.g., where UE 115-a also follows the logical rule to correctly decode the resulting DCI transmission 210) .
  • base station 105-a may reduce the DCI size for scheduling multiple transport blocks 215.
  • base station 105-a may not joint encode the scheduling parameter fields (e.g., the MCS field, the RV field, the repetition number field, etc. ) .
  • base station 105-a may jointly code the MCS, RV, and repetition number to save one bit of the DCI payload.
  • This bit may be used (e.g., concatenated with a HARQ process ID field and the multi-transport block flag) to indicate the number of scheduled transport blocks 215 and the associated HARQ process for each scheduled transport block 215.
  • Operating according to one of these example implementations may allow wireless communications system 200 to reduce the DCI payload for a DCI transmission 210 supporting single or multiple transport block 215 scheduling (e.g., where the resulting DCI payload is less than a DCI payload for individual or joint encoding) .
  • This lower DCI payload may correspondingly reduce the overhead on the control channel (e.g., downlink channel 205) .
  • FIG. 3 illustrates an example of a first DCI configuration 300 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the first DCI configuration 300 may support dynamically indicating up to two transport blocks in a same DCI transmission corresponding to two different error control processes (e.g., HARQ processes, automatic repeat request (ARQ) processes, or any other error detection processes associated with signal re-transmissions) .
  • the first DCI configuration 300 may additionally include an RV bit field 330 (e.g., indicating either a 0 bit value or a 1 bit value for a transport block) .
  • the DCI configuration 300 may correspond to multi-transport block scheduling for an uplink grant in an NB-IoT system.
  • Different DCI mappings 305 may be used by a base station 105 for the DCI bits based on different conditional states (e.g., whether multiple transport blocks are scheduled within the DCI configuration 300) .
  • a UE 115 receiving the DCI transmissions may determine the implemented DCI mapping 305 (e.g., based on a multi-transport block flag 310) and may determine the encoded information accordingly.
  • a base station 105 may indicate a subcarrier indication, a HARQ process number (e.g., a HARQ process ID or some other type of error control process identifier) , an NDI, and an RV for each transport block scheduled within a DCI transmission.
  • the subcarrier indication may be the same for each transport block scheduled within the same DCI.
  • a single subcarrier indication field 315 may be used to indicate the subcarrier indication for one transport block scheduled in the DCI or two transport blocks schedule in the DCI.
  • each scheduled transport block may correspond to a different HARQ process ID.
  • the scheduled transport blocks may correspond to the same or different NDIs, RVs, or both.
  • the base station 105 may implicitly or explicitly indicate the HARQ process IDs, NDIs, and RVs separately for the transport blocks (e.g., using different bit fields) .
  • the DCI configuration 300 may support twenty-five different states corresponding to the different combinations of HARQ processing IDs, NDIs, and RVs for transport block scheduling. These twenty-five states may generally correspond to three different categories, where the categories correspond to the number of scheduled transport blocks. In a first category, neither of the two possible transport blocks is scheduled in the DCI. In such a case, no scheduling is needed in DCI, so no DCI mapping 305 is needed. In a second category, one transport block is scheduled in the DCI. This category may correspond to eight different states (e.g., corresponding to all of the combinations for selecting one out of two possible HARQ process IDs, NDIs, and RVs) for single transport block scheduling.
  • Single transport block scheduling corresponds to DCI mappings 305-a and 305-c.
  • a third category two (i.e., both) transport blocks are scheduled in the DCI.
  • This category may correspond to sixteen different states (e.g., corresponding to all of the combinations for selecting one out of two possible NDIs and RVs for each of the transport blocks, as both HARQ process IDs are used in this case) for multi-transport block scheduling.
  • Multi-transport block scheduling corresponds to DCI mappings 305-b and 305-d, where DCI mappings 305-a and 305-b correspond to one implementation for scheduling and DCI mappings 305-c and 305-d correspond to a second implementation for scheduling.
  • the base station 105 may include a multiple transport block scheduling flag, which may be referred to as a multi-transport block flag 310.
  • This multi-transport block flag 310 may be an example of a one-bit bit field, where a first value of the bit field (e.g., a zero codepoint, such as a 0 bit value) indicates single transport block scheduling and a second value of the bit field (e.g., a non-zero codepoint, such as a 1 bit value) indicates multiple transport block scheduling.
  • a UE 115 receiving the DCI may determine the value of the multi-transport block flag 310 and may determine the DCI mapping 305 for the information based on this value.
  • the base station 105 may set the multi-transport block flag 310 to a 0 value.
  • the base station 105 may indicate the HARQ process ID, NDI, and RV for this one transport block using one-bit fields for each of these values.
  • the base station 105 may indicate the HARQ process ID using a HARQ process ID field 320-a, the NDI using an NDI field 325-a, and the RV using an RV field 330-a. Using these three one-bit fields, the base station 105 may indicate one of the possible eight states for single transport block scheduling.
  • the base station 105 may set the multi-transport block flag 310 to a 1 value, indicating a grant for multi-transport block scheduling.
  • the base station 105 may use four bits.
  • the three one-bit fields used for HARQ process ID, NDI, and RV indication in the single transport block DCI mapping 305 may not contain enough bit fields to support the sixteen possible states. Accordingly, the base station 105 may use an additional bit for HARQ process ID, NDI, and RV indication in the multiple transport block DCI mapping 305.
  • the base station 105 may use a bit field for NDI and RV indication when performing multi-transport block scheduling that is used for subcarrier indication when performing single transport block scheduling.
  • DCI mapping 305-a is used for the transport block scheduling information.
  • the information includes a six-bit subcarrier indication field 315-a, a one-bit HARQ process ID field 320-a, a one-bit NDI field 325-a, and a one-bit RV field 330-a (e.g., in addition to other fields) .
  • the base station 105 may apply a scheduling limitation to limit the resource assignment for multi-transport block scheduling. In this way, the base station 105 may reduce the subcarrier indication field 315-b to a five-bit field, where the most significant bit of the six-bit subcarrier indication field 315-ais reused for NDI or RV indication for the multiple transport blocks.
  • the reduction in the subcarrier indication field 315 size may result in limiting the set of subcarriers to select from for the transport blocks (e.g., for 3.75 kilohertz (kHz) subcarrier spacing (SCS) , the set of subcarriers may be reduced from 0-47 to 0-31) .
  • transport blocks e.g., for 3.75 kilohertz (kHz) subcarrier spacing (SCS)
  • the reduction in the subcarrier indication field 315 size may not affect the set of subcarriers to select from for the transport blocks, as the effective number of states is supported by the reduced field size and the most significant bit in the non-reduced field size is not used for any transport block scheduling (e.g., for 15 kHz SCS, the set of subcarriers 0-18 may be supported by either a five-bit or six-bit subcarrier indication field 315) .
  • the base station 105 may reuse the bit indicating the HARQ process ID in DCI mapping 305-a for NDI or RV indication in DCI mapping 305-b.
  • the base station 105 may have four bits to indicate the sixteen states for NDI and RV indication for the two transport blocks.
  • the base station 105 may use a first NDI field 325-b to indicate the NDI for the transport block corresponding to HARQ process #0 and may use a second NDI field 325-c to indicate the NDI for the transport block corresponding to HARQ process #1.
  • the base station 105 may use a first RV field 330-b to indicate the RV for the transport block corresponding to HARQ process #0 and may use a second RV field 330-c to indicate the RV for the transport block corresponding to HARQ process #1.
  • the HARQ process numbers are implicitly indicated while the NDI and RV are explicitly indicated for the multi-transport block scheduling.
  • DCI mapping 305-a and 305-b allows the base station 105 to maintain a same payload size for the transport block scheduling information independent of the number of transport blocks scheduled in the DCI transmission.
  • limiting the resource assignment for multi-transport block scheduling may allow for a reduced overhead for the DCI as compared to a joint coding technique.
  • a conventional system e.g., operating according to a “legacy” DCI format
  • scheduling a single transport block per DCI may use a number of bits, X, for transport block scheduling in DCI.
  • This first implementation may use X+1 bits to schedule two transport blocks per DCI, where the additional bit may be the multi-transport block grant flag, as compared to a joint coding technique for scheduling two transport blocks per DCI, which may use X+2 bits.
  • example DCI fields for the different conditional states are defined below.
  • the multi-transport block flag 310 equals 0 (e.g., for single transport block scheduling)
  • the DCI fields and corresponding bit-widths are defined in the Table below:
  • the DCI fields and corresponding bit-widths are defined in the Table below:
  • the base station 105 may use a bit field for NDI and RV indication when performing multi-transport block scheduling that is used for MCS indication when performing single transport block scheduling.
  • DCI mapping 305-c is used for the transport block scheduling information.
  • the information includes a four-bit MCS indication field 335-a, a one-bit HARQ process ID field 320-b, a one-bit NDI field 325-d, and a one-bit RV field 330-d (e.g., in addition to other fields) .
  • the base station 105 may apply a scheduling limitation to limit MCS options for multi-transport block scheduling. In this way, the base station 105 may reduce the MCS indication field 335-b to a three-bit field, limiting the number of MCS states to 8 for multi-transport block scheduling, as opposed to the number of states supported by the four-bit MCS indication field 335-a (e.g., 14 MCS states, or up to 16 MCS states) .
  • a base station 105 operating according to the second implementation may reuse the bit indicating the HARQ process ID in DCI mapping 305-c for NDI or RV indication in DCI mapping 305-d.
  • the base station 105 may have four bits to indicate the sixteen states for NDI and RV indication for the two transport blocks.
  • the base station 105 may use a first NDI field 325-e to indicate the NDI for the transport block corresponding to HARQ process #0 and may use a second NDI field 325-f to indicate the NDI for the transport block corresponding to HARQ process #1.
  • the base station 105 may use a first RV field 330-e to indicate the RV for the transport block corresponding to HARQ process #0 and may use a second RV field 330-f to indicate the RV for the transport block corresponding to HARQ process #1.
  • the base station 105 may simply include an additional bit in the DCI transmission. This bit may be unused for single transport block scheduling but may be used for NDI or RV indication in multi-transport block scheduling.
  • FIG. 4 illustrates an example of a second DCI configuration 400 that supports
  • the second DCI configuration 400 may support indicating up to eight transport blocks in a same DCI transmission corresponding to eight different error control processes (e.g., HARQ process numbers) .
  • the second DCI configuration 400 may correspond to multi-transport block scheduling for an uplink or downlink grant in CE mode A for eMTC.
  • CE mode A may correspond, for example, to a first coverage level (e.g., normal coverage) .
  • Different DCI mappings 405 may be used at a base station 105 for the DCI bits based on different conditional states (e.g., whether a single or multiple transport blocks are scheduled within the DCI configuration 400) .
  • a UE 115 receiving the DCI transmission may determine the implemented DCI mapping 405 (e.g., based on a multi-transport block flag 410) and, accordingly, the indicated transport block scheduling information.
  • CE Mode A for eMTC may support scheduling for up to eight transport blocks within a single DCI transmission.
  • a base station 105 may select a common NDI, a common RV, or both for all transport blocks scheduled in a same DCI.
  • the base station 105 may reuse bits that correspond to other DCI fields for single transport block scheduling in order to further reduce the DCI size needed for multi-transport block scheduling. For example, when multiple transport blocks are scheduled in a DCI transmission, the base station 105 may limit the combinations of MCS, RV, repetition number, or some combination of these to reduce the number of bits used to indicate these parameters.
  • DCI mapping 405-a may be used, including a two-bit repetition number field 420, a two-bit RV field 425, and a four-bit MCS field 430 resulting in eight bits to indicate these three values (e.g., where each value is indicated separately) .
  • DCI mapping 405-b may be used, where the repetition number, RV, and MCS values may be jointly coded in a seven-bit field 440. Therefore, DCI mapping 405-b uses one less bit for repetition number, RV, and MCS indication than DCI mapping 405-a. This one bit may instead be used for indicating the scheduling of the multiple transport blocks (e.g., to indicate the number of transport blocks scheduled, a respective error control process number such as the HARQ process ID for each scheduled transport block, etc. ) .
  • the base station 105 may set the field value of this multi-transport block flag 410 to a zero codepoint (e.g., ⁇ 0 0 0 0 ⁇ for a four-bit field) to indicate scheduling for a single transport block in the DCI.
  • the base station 105 may use DCI mapping 405-a to schedule this single transport block.
  • DCI mapping 405-a may include a three-bit HARQ process number field 415, a two-bit repetition number field 420, a two-bit RV field 425, and a four-bit MCS field 430 for indicating these parameters for the single transport block.
  • the base station 105 may set the field value of the multi-transport block flag 410 to a non-zero codepoint to indicate a grant for multi-transport block scheduling.
  • the base station 105 may use DCI mapping 405-b to schedule the multiple transport blocks.
  • the base station 105 may jointly code the MCS, RV, and repetition number to calculate a seven-bit value and may indicate this jointly coded value in a seven-bit jointly coded repetition number, RV, and MCS field 440.
  • the base station 105 may concatenate the four bits used for the multi-transport block flag 410, the three bits used for the HARQ process number field 415 in DCI mapping 405-a, and the one bit saved from the MCS, RV, and repetition number joint encoding (e.g., bit a0) to generate an eight-bit field for DCI mapping 405-b, where the four bits from the multi-transport block flag 410 may be the most significant bits of this concatenated bit field 435.
  • the base station 105 may jointly indicate the scheduled number of transport blocks (e.g., two transport blocks, three transport blocks, etc., up to eight transport blocks) and the associated HARQ process IDs for these transport blocks in this eight-bit field 435.
  • the eight-bit field 435 may not include enough bit combinations to indicate each of these possible states.
  • the eight-bit field 435 may indicate any codepoint where the multi-transport block flag 410-b is not ⁇ 0 0 0 0 ⁇ , resulting in 15 possible non-zero codepoints for the four-bit flag.
  • the base station 105 may drop 7 states from the 247 possible states for multi-transport block scheduling in order to support transport block scheduling in the eight-bit field 435.
  • the number of bits in the DCI can be further reduced or the full set of HARQ process states may be supported, as the number of combinations of number of transport blocks and associated HARQ process IDs is reduced.
  • This second DCI configuration 400 may reduce the DCI payload by one bit-and, thus, reduce the DCI overhead-as compared to simply restricting transport blocks to a common NDI and RV.
  • jointly encoding the repetition number, RV, and MCS for a set of transport blocks scheduled in the same DCI may involve applying a scheduling limitation on one or more of the parameters.
  • the following table illustrates an example joint coding scheme for these parameters:
  • the base station 105 may select the RV value to indicate from up to four different RV values (e.g., corresponding to the two-bit field) and may select the MCS to indicate from up to sixteen different MCSs (e.g., corresponding to the four-bit field) .
  • those fields are reduced to one bit and three bits respectively, supporting selection of the RV value from up to two different RV values and the MCS from up to eight different MCSs.
  • a larger repetition number may often be used for transport blocks when a UE 115 is in poor coverage by the base station 105.
  • a base station 105 may use low MCS levels and low coding rates to improve the transmission reliabilities.
  • lowering the number of RV and MCS options may not significantly affect the base station 105 selections due to the base station 105 commonly using a small subset of these values when the repetition number is high.
  • jointly indicating the number of transport blocks and the associated HARQ process number for each transport block may involve indicating a combination index value, i.
  • the combination index value i may correspond to the decimal number (e.g., the codepoint) jointly indicated in the concatenated eight-bit field 435.
  • the value of i may directly correspond to the number of transport blocks scheduled in the DCI according to the following table:
  • the value range for each number of transport blocks may not correspond to the respective number of combinations for that number of transport blocks (e.g., to support indication in the eight-bit field 435 according to the non-zero codepoint constraint for the multi-transport block flag 410-b) .
  • the base station 105 may apply a scheduling limitation for the supported HARQ process IDs for scheduling two transport blocks such that the set of supported HARQ process IDs for scheduling two transport blocks may be indicated using 21 values in the range 16 ⁇ i ⁇ 37.
  • Alternative HARQ process ID limitations may be supported than those shown in the above Table.
  • a UE 115 receiving the DCI transmission may determine that the DCI transmission uses DCI mapping 405-b based on the value of the multi-transport block flag 410-b corresponding to a non-zero codepoint. The UE 115 may then determine the combination index value i contained in the jointly indicated number of transport blocks and associated HARQ process IDs field 435. The UE 115 may use this identified value, i, (i.e., the decimal value of the concatenated eight-bit field 435, where 16 ⁇ i ⁇ 256) in a procedure to determine the associated HARQ process number for each of the scheduled transport blocks, where the number of scheduled transport blocks, M, follows 2 ⁇ M ⁇ 8.
  • i i.e., the decimal value of the concatenated eight-bit field 435, where 16 ⁇ i ⁇ 256
  • the UE 115 may determine the value of M according to a table in memory (e.g., based on the above table, where the number of transport blocks is determined based on the value range that i falls within) .
  • i′ indicates a selection of M elements from a vector of size N, with This corresponds to the selection of M HARQ process numbers out of the N possible HARQ process numbers corresponding to the scheduled transport blocks.
  • the UE 115 may determine the set of HARQ process numbers, where 1 ⁇ m ⁇ M and such that These values denote the HARQ process numbers for the M scheduled transport blocks.
  • This procedure for determining the HARQ process number (e.g., ID) associated with each scheduled transport block based on a calculated combination index value, i′ may alternatively be described using the following pseudocode:
  • values for the function may be defined in a lookup table stored in memory (e.g., at a UE 115, a base station 105, etc. ) , presented below:
  • a UE 115 may receive a DCI transmission with multiple scheduled transport blocks.
  • a base station 105 may perform a similar process (e.g., an inverse of the process) to initially determine i′ and i based on the selected HARQ process IDs for the multiple transport blocks.
  • FIG. 5 illustrates an example of a third DCI configuration 500 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the third DCI configuration 500 may support indicating up to four transport blocks in a same DCI transmission corresponding to four different error control processes (e.g., HARQ process numbers) .
  • the third DCI configuration 500 may correspond to multi-transport block scheduling for an uplink or downlink grant in CE mode B for eMTC.
  • Different DCI mappings 505 may be used at a base station 105 for the DCI bits based on different conditional states (e.g., whether a single or multiple transport blocks are scheduled within the DCI configuration 500) .
  • a UE 115 receiving the DCI transmissions may determine the implemented DCI mapping 505 (e.g., based on a multi-transport block flag 510) and, accordingly, the indicated transport block scheduling information.
  • CE Mode B for eMTC may support scheduling for up to four transport blocks within a single DCI transmission.
  • CD Mode B may correspond, for example, to a second coverage level (e.g., enhanced coverage) .
  • a base station 105 may perform similar techniques as described with respect to FIG. 5 to handle multi-transport block scheduling in a DCI transmission. However, rather than a four-bit field for the multi-transport block flag, in the third DCI configuration 500 the base station 105 may include a one-bit multi-transport block flag 510 (e.g., according to the N-1-log 2 N bit-width for the flag) .
  • DCI mapping 505-a may include a two-bit HARQ process ID field 515, a three-bit repetition number field 520, and a four-bit MCS field 525.
  • the base station 105 may use DCI mapping 505-b. In DCI mapping 505-b, the base station 105 may jointly code the repetition number and MCS in field 535 using six bits.
  • the bit saved from this joint coding may be concatenated with the multi-transport block flag 510-b bit and the two-bit HARQ process ID field 515 to form a four-bit field 530 for jointly indicating the number of transport blocks scheduled and the associated HARQ process IDs, where the multi-transport block flag 510-b may correspond to the most significant bit of the bit field 530.
  • a mapping table for determining the number of scheduled transport blocks based on the received combination index value in field 530 is presented below:
  • the value ranges may not contain the full set of combinations.
  • the base station 105 may limit the number of states for scheduling two transport blocks to three states, as opposed to six possible states.
  • the joint coding of the repetition number and MCS may be defined by the following table:
  • FIG. 6 illustrates an example of a process flow 600 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the process flow 600 may include a base station 105-b and a UE 115-b, which may be examples of the corresponding devices described with reference to FIGs. 1 and 2.
  • Base station 105-b may transmit a DCI transmission (e.g., a PDCCH, MPDDCH, or NPDCCH transmission) that can schedule multiple transport blocks for UE 115-b.
  • base station 105-b may utilize scheduling limitations and encoding of information based on whether multiple transport blocks are scheduled in the DCI.
  • Alternative examples of the following may be implemented, where some steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.
  • base station 105-b may determine a number of transport blocks to schedule within a DCI transmission. If multiple transport blocks are to be scheduled within the DCI transmission, each transport block may correspond to a different TTI, a different HARQ process, or both. Base station 105-b may dynamically schedule the transport blocks within the DCI.
  • base station 105-b may determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks (e.g., based on whether multiple transport blocks are scheduled in the DCI transmission) .
  • the payload size of the information may be the same for scheduling different numbers of transport blocks within the DCI transmission (e.g., based on the applied scheduling limitation) .
  • base station 105-b may limit a set of subcarrier resources for subcarrier resource assignment for scheduling the multiple transport blocks based on the multiple transport blocks being scheduled in a single DCI transmission. In some cases, if the number of transport blocks to schedule is greater than one, base station 105-b may indicate an NDI value for one of the transport blocks using a first bit position in the information that is associated with indicating a HARQ process number (e.g., a HARQ process ID) when scheduling a single transport block in the DCI.
  • a HARQ process number e.g., a HARQ process ID
  • base station 105-b may jointly encode at least a portion of the information for the DCI transmission.
  • a bit position of the jointly encoded portion of information may be associated with an MCS when the number of transport blocks to schedule is one.
  • base station 105-b may jointly encode an MCS, an RV, a repetition number, or some combination of these for scheduling multiple transport blocks within the DCI transmission.
  • determining whether to apply the scheduling limitation may involve base station 105-b selecting the repetition number for scheduling the multiple transport blocks, limiting a number of MCSs, RVs, or both based on the repetition number, and selecting the MCS, RV, or both for scheduling from the corresponding limited set.
  • the joint encoding may involve jointly encoding the number of transport blocks to schedule with the respective HARQ process numbers (e.g., IDs) for each of these transport blocks.
  • base station 105-b may determine a combination index, i, based on the respective HARQ process numbers for each transport block and a table stored in memory, an equation stored in memory, or some combination of these.
  • This combination index may indicate the number of transport blocks to schedule and the respective HARQ process numbers for each transport block and may be included in the information to encode for the DCI transmission.
  • the respective HARQ process numbers for the transport blocks may be indicated sequentially in an increasing order.
  • a scheduling limitation may reduce the number of possible combinations of numbers of transport blocks and corresponding HARQ process numbers.
  • base station 105-b may encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied.
  • the information may contain at least a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • a first value e.g., a zero codepoint
  • a second value e.g., a non-zero codepoint
  • the flag indicates that multiple transport blocks are scheduled within the DCI transmission. For example, if the flag contains a single bit, a 0 bit value may indicate single transport block scheduling and a 1 bit value may indicate multi-transport block scheduling.
  • a first set of bits may indicate single transport block scheduling while any other set of bits may indicate multi-transport block scheduling.
  • base station 105-b may jointly encode the flag with at least a portion of the information (e.g., the transport block scheduling information for the DCI) .
  • the flag may be jointly encoded as the most significant bits of the jointly encoded set of bits (e.g., to maximize the number of different states that can be indicated by the jointly encoded set of bits) .
  • base station 105-b may transmit the encoded information in the DCI transmission.
  • UE 115-b may receive the encoded information in a DCI transmission.
  • UE 115-b may decode, from the encoded information, the flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • UE 115-b may decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission. For example, if multiple transport blocks are scheduled in the DCI transmission, UE 115-b may identify an NDI value for one of the scheduled transport blocks using a first bit position in the transport block scheduling information, where the first bit position is associated with a HARQ process number when a single transport block is scheduled. Additionally, UE 115-b may identify an RV value for one of the scheduled transport blocks using a second bit position in the transport block scheduling information, where the second bit position is associated with a subcarrier resource assignment when a single transport block is scheduled.
  • UE 115-b may jointly decode at least a portion of the transport block scheduling information based on the multi-transport block DCI. For example, UE 115-b may jointly decode information according to the implemented process for joint encoding at base station 105-b.
  • the encoded information may have a same payload size independent of the number of transport blocks scheduled in the DCI.
  • UE 115-b may identify one or more scheduled transport blocks (e.g., including corresponding HARQ process IDs, repetition numbers, NDIs, RVs, MCSs, or some combination of these parameters) based on the transport block scheduling information.
  • each transport block scheduled within the DCI transmission may correspond to a common NDI value and a common RV value.
  • each transport block scheduled within the DCI transmission may correspond to a different TTI (e.g., a different subframe, slot, mini-slot, symbol, etc. ) , a different HARQ process, or both.
  • base station 105-b may transmit downlink information or receive uplink information in one or more of the transport blocks scheduled within the DCI transmission, and UE 115-b may receive the downlink information or transmit the uplink information based on identifying the scheduled transport blocks.
  • FIG. 7 shows a block diagram 700 of a device 705 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 705 may be an example of aspects of a UE 115 as described herein.
  • the device 705 may include a receiver 710, a DCI manager 715, and a transmitter 720.
  • the device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 710 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 DCI design for scheduling of multiple transport blocks, etc. ) . Information may be passed on to other components of the device 705.
  • the receiver 710 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the receiver 710 may utilize a single antenna or a set of antennas.
  • the DCI manager 715 may receive encoded information in a DCI transmission, decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the DCI manager 715 may be an example of aspects of the DCI manager 1010 described herein.
  • the DCI manager 715 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the DCI manager 715, or its sub-components may be executed 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 the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the DCI manager 715 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the DCI manager 715 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • DCI manager 715 may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the DCI manager 715, or its sub-components may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • I/O input/output
  • the transmitter 720 may transmit signals generated by other components of the device 705.
  • the transmitter 720 may be collocated with a receiver 710 in a transceiver.
  • the transmitter 720 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the transmitter 720 may utilize a single antenna or a set of antennas.
  • FIG. 8 shows a block diagram 800 of a device 805 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 805 may be an example of aspects of a device 705, or a UE 115 as described herein.
  • the device 805 may include a receiver 810, a DCI manager 815, and a transmitter 840.
  • the device 805 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • the receiver 810 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 DCI design for scheduling of multiple transport blocks, etc. ) . Information may be passed on to other components of the device 805.
  • the receiver 810 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the receiver 810 may utilize a single antenna or a set of antennas.
  • the DCI manager 815 may be an example of aspects of the DCI manager 715 as described herein.
  • the DCI manager 815 may include a reception component 820, a flag identifier 825, a decoder 830, and a scheduled transport block identifier 835.
  • the DCI manager 815 may be an example of aspects of the DCI manager 1010 described herein.
  • the reception component 820 may receive encoded information in a DCI transmission.
  • the reception component 820 may monitor (e.g., blind decoding) a downlink control channel or control region (e.g., control resource set (CORESET) ) according to one or more search space sets and/or radio network temporary identifiers (RNTIs) and identify the encoded information in the DCI transmission (e.g., by a passing error check for an error check field of a decoded DCI transmission) .
  • CORESET control resource set
  • RNTIs radio network temporary identifiers
  • the flag identifier 825 may decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the decoder 830 may decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission.
  • the scheduled transport block identifier 835 may identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the transmitter 840 may transmit signals generated by other components of the device 805.
  • the transmitter 840 may be collocated with a receiver 810 in a transceiver.
  • the transmitter 840 may be an example of aspects of the transceiver 1020 described with reference to FIG. 10.
  • the transmitter 840 may utilize a single antenna or a set of antennas.
  • FIG. 9 shows a block diagram 900 of a DCI manager 905 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the DCI manager 905 may be an example of aspects of a DCI manager 715, a DCI manager 815, or a DCI manager 1010 described herein.
  • the DCI manager 905 may include a reception component 910, a flag identifier 915, a decoder 920, a scheduled transport block identifier 925, a joint decoding component 930, a combination index component 935, and a common payload size component 940.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the reception component 910 may receive encoded information in a DCI transmission.
  • the reception component 910 may monitor (e.g., blind decoding) a downlink control channel or control region (e.g., control resource set (CORESET) ) according to one or more search space sets and identify the encoded information in the DCI transmission.
  • CORESET control resource set
  • the flag identifier 915 may decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • a first value e.g., a zero codepoint
  • a second value e.g., a non-zero codepoint
  • the decoder 920 may decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission.
  • the decoder 920 may identify a new data indicator value for one of the one or more scheduled transport blocks using a first bit position in the transport block scheduling information, where the first bit position is associated with a hybrid automatic repeat request process number when multiple transport blocks are not scheduled.
  • the decoder 920 may identify a redundancy version for one of the one or more scheduled transport blocks using a second bit position in the transport block scheduling information, where the second bit position is associated with a subcarrier resource assignment when multiple transport blocks are not scheduled.
  • the scheduled transport block identifier 925 may identify one or more scheduled transport blocks based on the transport block scheduling information. In some examples, the scheduled transport block identifier 925 may identify that multiple transport blocks are scheduled within the DCI transmission. In some cases, each transport block scheduled within the DCI transmission corresponds to a common new data indicator value and a common redundancy version value.
  • each transport block scheduled within the DCI transmission corresponds to a different transmission time interval. In some cases, each transport block scheduled within the DCI transmission corresponds to a different hybrid automatic repeat request process.
  • the joint decoding component 930 may jointly decode at least a portion of the transport block scheduling information based on multiple transport blocks being scheduled within the DCI transmission. In some examples, the joint decoding component 930 may jointly decode the flag (e.g., the non-zero codepoint value for the flag) and at least the portion of the transport block scheduling information. In some examples, the joint decoding component 930 may jointly decode a modulation and coding scheme, a redundancy version, a repetition number, or some combination thereof for the multiple transport blocks based on the multiple transport blocks being scheduled within the DCI transmission. In some examples, the joint decoding component 930 may determine the repetition number.
  • the joint decoding component 930 may determine a number of bits indicating the modulation and coding scheme, a number of bits indicating the redundancy version, or both based on the determined repetition number. In some examples, the joint decoding component 930 may jointly decode a number of scheduled transport blocks and respective hybrid automatic repeat request process numbers for each of the multiple transport blocks. In some cases, a bit position of the transport block scheduling information that is jointly decoded is associated with a modulation and coding scheme when multiple transport blocks are not scheduled.
  • the combination index component 935 may decode a combination index based on a table stored in a memory, an equation stored in the memory, or a combination thereof, where the combination index indicates the number of scheduled transport blocks and the respective hybrid automatic repeat request process numbers for each of the multiple transport blocks. In some cases, the respective hybrid automatic repeat request process numbers for the multiple transport blocks are indicated sequentially in an increasing order.
  • the common payload size component 940 may identify a payload size corresponding to the encoded information, where the payload size is the same for different numbers of transport blocks scheduled within the DCI transmission.
  • the reception component 910 may receive downlink information in the identified one or more transport blocks.
  • FIG. 10 shows a diagram of a system 1000 including a device 1005 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 1005 may be an example of or include the components of device 705, device 805, or a UE 115 as described herein.
  • the device 1005 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a DCI manager 1010, an I/O controller 1015, a transceiver 1020, an antenna 1025, memory 1030, and a processor 1040. These components may be in electronic communication via one or more buses (e.g., bus 1045) .
  • buses e.g., bus 1045
  • the DCI manager 1010 may receive encoded information in a DCI transmission, decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission, and identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the I/O controller 1015 may manage input and output signals for the device 1005.
  • the I/O controller 1015 may also manage peripherals not integrated into the device 1005.
  • the I/O controller 1015 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1015 may utilize an operating system such as MS- MS- OS/ or another known operating system.
  • the I/O controller 1015 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device.
  • the I/O controller 1015 may be implemented as part of a processor.
  • a user may interact with the device 1005 via the I/O controller 1015 or via hardware components controlled by the I/O controller 1015.
  • the transceiver 1020 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1020 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1020 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1025. However, in some cases the device may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1030 may include random-access memory (RAM) and read-only memory (ROM) .
  • the memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1030 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic input/output system
  • the processor 1040 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) .
  • the processor 1040 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1040.
  • the processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks supporting DCI design for scheduling of multiple transport blocks) .
  • the code 1035 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1035 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • FIG. 11 shows a block diagram 1100 of a device 1105 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 1105 may be an example of aspects of a base station 105 as described herein.
  • the device 1105 may include a receiver 1110, a DCI manager 1115, and a transmitter 1120.
  • the device 1105 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • 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 DCI design for scheduling of multiple transport blocks, etc. ) . Information may be passed on to other components of the device 1105.
  • the receiver 1110 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the receiver 1110 may utilize a single antenna or a set of antennas.
  • the DCI manager 1115 may determine a number of transport blocks to schedule within a DCI transmission, determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmit the encoded information in the DCI transmission.
  • the DCI manager 1115 may be an example of aspects of the DCI manager 1410 described herein.
  • the DCI manager 1115 may be implemented in hardware, code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the DCI manager 1115, or its sub-components may be executed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC) , a 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 the present disclosure.
  • code e.g., software or firmware
  • ASIC application-specific integrated circuit
  • the DCI manager 1115 may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components.
  • the DCI manager 1115, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the DCI manager 1115, or its sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.
  • the transmitter 1120 may transmit signals generated by other components of the device 1105.
  • the transmitter 1120 may be collocated with a receiver 1110 in a transceiver.
  • the transmitter 1120 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the transmitter 1120 may utilize a single antenna or a set of antennas.
  • FIG. 12 shows a block diagram 1200 of a device 1205 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of aspects of a device 1105, or a base station 105 as described herein.
  • the device 1205 may include a receiver 1210, a DCI manager 1215, and a transmitter 1240.
  • the device 1205 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
  • 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 DCI design for scheduling of multiple transport blocks, etc. ) . Information may be passed on to other components of the device 1205.
  • the receiver 1210 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the receiver 1210 may utilize a single antenna or a set of antennas.
  • the DCI manager 1215 may be an example of aspects of the DCI manager 1115 as described herein.
  • the DCI manager 1215 may include a transport block scheduler 1220, a scheduling limitation determination component 1225, an encoder 1230, and a transmission component 1235.
  • the DCI manager 1215 may be an example of aspects of the DCI manager 1410 described herein.
  • the transport block scheduler 1220 may determine a number of transport blocks to schedule within a DCI transmission.
  • the scheduling limitation determination component 1225 may determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks.
  • the encoder 1230 may encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the transmission component 1235 may transmit the encoded information in the DCI transmission.
  • the encoded information may be transmitted via a downlink control channel to a UE 115.
  • the DCI may schedule downlink or uplink transmissions.
  • the transmitter 1240 may transmit signals generated by other components of the device 1205.
  • the transmitter 1240 may be collocated with a receiver 1210 in a transceiver.
  • the transmitter 1240 may be an example of aspects of the transceiver 1420 described with reference to FIG. 14.
  • the transmitter 1240 may utilize a single antenna or a set of antennas.
  • FIG. 13 shows a block diagram 1300 of a DCI manager 1305 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the DCI manager 1305 may be an example of aspects of a DCI manager 1115, a DCI manager 1215, or a DCI manager 1410 described herein.
  • the DCI manager 1305 may include a transport block scheduler 1310, a scheduling limitation determination component 1315, an encoder 1320, a transmission component 1325, a subcarrier resource limitation component 1330, a joint encoding component 1335, a combination index component 1340, and a common payload size component 1345.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the transport block scheduler 1310 may determine a number of transport blocks to schedule within a DCI transmission. In some cases, the number of transport blocks to schedule is greater than one. In some cases, each transport block scheduled within the DCI transmission corresponds to a different transmission time interval. In some cases, each transport block scheduled within the DCI transmission corresponds to a different hybrid automatic repeat request process.
  • the scheduling limitation determination component 1315 may determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks. In some examples, the scheduling limitation determination component 1315 may limit each transport block scheduled within the DCI transmission to a common new data indicator value and a common redundancy version value.
  • the encoder 1320 may encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the encoder 1320 may indicate a new data indicator value for one of the transport blocks using a first bit position in the information, where the first bit position is associated with a hybrid automatic repeat request process number when the number of transport blocks to schedule is one. In some examples, the encoder 1320 may indicate a redundancy version for one of the transport blocks using a second bit position in the information, where the second bit position is associated with a subcarrier resource assignment when the number of transport blocks to schedule is one.
  • a first value (e.g., a zero codepoint) for the flag indicates that one transport block is scheduled within the DCI transmission and a second value (e.g., a non-zero codepoint) for the flag indicates that multiple transport blocks are scheduled within the DCI transmission.
  • the transmission component 1325 may transmit the encoded information in the DCI transmission. In some examples, the transmission component 1325 may transmit downlink data in one or more transport blocks scheduled within the DCI transmission. In some examples, the DCI manager 1305 may receive uplink data in one or more transport blocks scheduled within the DCI transmission.
  • the subcarrier resource limitation component 1330 may limit a set of subcarrier resources for subcarrier resource assignment for scheduling multiple transport blocks within the DCI transmission based on the number of transport blocks to schedule being greater than one. In some examples, selecting a subcarrier resource for the multiple transport blocks from the limited set of subcarrier resources, where the information includes the selected subcarrier resource.
  • the joint encoding component 1335 may jointly encode at least a portion of the information for the DCI transmission based on the number of transport blocks to schedule being greater than one. In some examples, the joint encoding component 1335 may jointly encode the flag (e.g., the non-zero codepoint value for the flag) with at least the portion of the information. In some examples, the joint encoding component 1335 may jointly encode a modulation and coding scheme, a redundancy version, a repetition number, or some combination thereof for scheduling multiple transport blocks within the DCI transmission based on the number of transport blocks to schedule being greater than one. In some examples, the joint encoding component 1335 may select the repetition number for scheduling the multiple transport blocks.
  • the joint encoding component 1335 may limit a number of modulation and coding schemes, a number of redundancy versions, or both based on the repetition number. In some examples, the joint encoding component 1335 may select the modulation and coding scheme from the limited number of modulation and coding schemes, the redundancy version from the limited number of redundancy versions, or both for scheduling the multiple transport blocks. In some examples, the joint encoding component 1335 may jointly encode the number of transport blocks to schedule and respective hybrid automatic repeat request process numbers for each transport block. In some cases, a bit position of at least the portion of the information that is jointly encoded is associated with a modulation and coding scheme when the number of transport blocks to schedule is one.
  • the combination index component 1340 may determine a combination index based on the respective hybrid automatic repeat request process number for each transport block, a table stored in a memory, an equation stored in the memory, or a combination thereof, where the combination index indicates the number of transport blocks to schedule and the respective hybrid automatic repeat request process number for each transport block, where the information includes the combination index.
  • the respective hybrid automatic repeat request process numbers for the transport blocks are indicated sequentially in an increasing order.
  • the common payload size component 1345 may identify a payload size for the information for the DCI transmission, where the payload size is the same for scheduling different numbers of transport blocks within the DCI transmission.
  • FIG. 14 shows a diagram of a system 1400 including a device 1405 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the device 1405 may be an example of or include the components of device 1105, device 1205, or a base station 105 as described herein.
  • the device 1405 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a DCI manager 1410, a network communications manager 1415, a transceiver 1420, an antenna 1425, memory 1430, a processor 1440, and an inter-station communications manager 1445. These components may be in electronic communication via one or more buses (e.g., bus 1450) .
  • buses e.g., bus 1450
  • the DCI manager 1410 may determine a number of transport blocks to schedule within a DCI transmission, determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks, encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission, and transmit the encoded information in the DCI transmission.
  • the network communications manager 1415 may manage communications with the core network 130 (e.g., via one or more wired backhaul links) .
  • the network communications manager 1415 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the transceiver 1420 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1420 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1420 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.
  • the wireless device may include a single antenna 1425. However, in some cases the device may have more than one antenna 1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1430 may include RAM, ROM, or a combination thereof.
  • the memory 1430 may store computer-readable code 1435 including instructions that, when executed by a processor (e.g., the processor 1440) cause the device to perform various functions described herein.
  • a processor e.g., the processor 1440
  • the memory 1430 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • 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) .
  • the processor 1440 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into processor 1440.
  • the processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1430) to cause the device 1405 to perform various functions (e.g., functions or tasks supporting DCI design for scheduling of multiple transport blocks) .
  • the inter-station communications manager 1445 may manage communications with other base station 105 and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communications manager 1445 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager 1445 may provide an X2 interface within an LTE/LTE-Awireless communication network technology to provide communication between base stations 105.
  • the code 1435 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1435 may be stored in a non-transitory computer-readable medium such as system memory or other type 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 functions described herein.
  • FIG. 15 shows a flowchart illustrating a method 1500 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1500 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1500 may be performed by a DCI manager as described with reference to FIGs. 11 through 14.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may determine a number of transport blocks to schedule within a DCI transmission.
  • the operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be performed by a transport block scheduler as described with reference to FIGs. 11 through 14.
  • the base station may determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks.
  • the operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed by a scheduling limitation determination component as described with reference to FIGs. 11 through 14.
  • the base station may encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be performed by an encoder as described with reference to FIGs. 11 through 14.
  • the base station may transmit the encoded information in the DCI transmission.
  • the operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1520 may be performed by a transmission component as described with reference to FIGs. 11 through 14.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1600 may be implemented by a base station 105 or its components as described herein.
  • the operations of method 1600 may be performed by a DCI manager as described with reference to FIGs. 11 through 14.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.
  • the base station may determine a number of transport blocks to schedule within a DCI transmission.
  • the operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be performed by a transport block scheduler as described with reference to FIGs. 11 through 14.
  • the base station may determine whether to apply a scheduling limitation to information for the DCI transmission based on the number of transport blocks.
  • the operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be performed by a scheduling limitation determination component as described with reference to FIGs. 11 through 14.
  • the base station may identify a payload size for the information for the DCI transmission, where the payload size is the same for scheduling different numbers of transport blocks within the DCI transmission.
  • the operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of
  • 1615 may be performed by a common payload size component as described with reference to FIGs. 11 through 14.
  • the base station may encode the information for the DCI transmission based on the number of transport blocks and whether the scheduling limitation is applied, where the information includes a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1620 may be performed according to the methods described herein. In some examples, aspects of the operations of 1620 may be performed by an encoder as described with reference to FIGs. 11 through 14.
  • the base station may transmit the encoded information in the DCI transmission.
  • the operations of 1625 may be performed according to the methods described herein. In some examples, aspects of the operations of 1625 may be performed by a transmission component as described with reference to FIGs. 11 through 14.
  • the base station may transmit downlink information in one or more transport blocks scheduled within the DCI transmission.
  • the operations of 1630 may be performed according to the methods described herein. In some examples, aspects of the operations of 1630 may be performed by a transmission component as described with reference to FIGs. 11 through 14.
  • FIG. 17 shows a flowchart illustrating a method 1700 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1700 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1700 may be performed by a DCI manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may receive encoded information in a DCI transmission.
  • the operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed by a reception component as described with reference to FIGs. 7 through 10.
  • the UE may decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed by a flag identifier as described with reference to FIGs. 7 through 10.
  • the UE may decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed by a decoder as described with reference to FIGs. 7 through 10.
  • the UE may identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed by a scheduled transport block identifier as described with reference to FIGs. 7 through 10.
  • FIG. 18 shows a flowchart illustrating a method 1800 that supports DCI design for scheduling of multiple transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1800 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1800 may be performed by a DCI manager as described with reference to FIGs. 7 through 10.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.
  • the UE may receive encoded information in a DCI transmission.
  • the operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed by a reception component as described with reference to FIGs. 7 through 10.
  • the UE may identify a payload size corresponding to the encoded information, where the payload size is the same for different numbers of transport blocks scheduled within the DCI transmission.
  • the operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed by a common payload size component as described with reference to FIGs. 7 through 10.
  • the UE may decode, from the encoded information, a flag indicating whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed by a flag identifier as described with reference to FIGs. 7 through 10.
  • the UE may decode, from the encoded information, transport block scheduling information based on whether multiple transport blocks are scheduled within the DCI transmission.
  • the operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed by a decoder as described with reference to FIGs. 7 through 10.
  • the UE may identify one or more scheduled transport blocks based on the transport block scheduling information.
  • the operations of 1825 may be performed according to the methods described herein. In some examples, aspects of the operations of 1825 may be performed by a scheduled transport block identifier as described with reference to FIGs. 7 through 10.
  • the UE may receive downlink information in the identified one or more transport blocks.
  • the operations of 1830 may be performed according to the methods described herein. In some examples, aspects of the operations of 1830 may be performed by a reception component as described with reference to FIGs. 7 through 10.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • a CDMA system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc.
  • CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
  • IS-2000 Releases may be commonly referred to as CDMA2000 1X, 1X, etc.
  • IS-856 TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • a TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • 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, Flash-OFDM, etc.
  • UMB Ultra Mobile Broadband
  • E-UTRA Evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDM
  • UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS) .
  • LTE, LTE-A, and LTE-A Pro are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from the organization named “3rd Generation Partnership Project” (3GP
  • CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • 3GPP2 3rd Generation Partnership Project 2
  • the techniques described herein may be used for the systems and radio technologies mentioned herein as well as other systems and radio technologies. While aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell may be associated with a lower-powered base station, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed, etc. ) frequency bands as macro cells.
  • Small cells may include pico cells, femto cells, and micro cells according to various examples.
  • a pico cell for example, may cover a small geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) .
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB.
  • An eNB may support one or multiple (e.g., two, three, four, and the like) cells, and may also support communications using one or multiple component carriers.
  • the wireless communications systems described herein may support synchronous or asynchronous operation.
  • the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time.
  • the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time.
  • the techniques described herein may be used for either synchronous or asynchronous operations.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

Landscapes

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

Abstract

La présente invention concerne une conception d'Informations de commande de liaison descendante (DCI) pour la planification de multiples blocs de transport. Une taille de charge utile de DCI commune peut être configurée pour prendre en charge la planification d'un certain nombre de blocs de transport (par exemple, un ou jusqu'à un nombre maximum) avec un codage d'état conditionnel. Une station de base peut déterminer un nombre de blocs de transport à planifier, et déterminer s'il faut appliquer une limitation de planification à des informations utilisées pour programmer les blocs de transport sur la base du nombre de blocs de transport. La station de base peut ensuite coder les informations à l'aide de champs DCI codés de manière conditionnelle sur la base du nombre de blocs de transport et de la limitation de planification. Les informations peuvent comprendre un drapeau indiquant si de multiples blocs de transport sont programmés. La station de base peut transmettre les DCI codées et un UE peut décoder les DCI selon le drapeau et les champs DCI codés de manière conditionnelle pour déterminer les informations utilisées pour programmer les blocs de transport.
PCT/CN2018/120924 2018-12-13 2018-12-13 Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport WO2020118632A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/120924 WO2020118632A1 (fr) 2018-12-13 2018-12-13 Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/120924 WO2020118632A1 (fr) 2018-12-13 2018-12-13 Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport

Publications (1)

Publication Number Publication Date
WO2020118632A1 true WO2020118632A1 (fr) 2020-06-18

Family

ID=71075888

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/120924 WO2020118632A1 (fr) 2018-12-13 2018-12-13 Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport

Country Status (1)

Country Link
WO (1) WO2020118632A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112514316A (zh) * 2020-10-14 2021-03-16 北京小米移动软件有限公司 联合调度多个传输块的方法、装置、通信设备及存储介质
EP4039028A4 (fr) * 2019-10-04 2023-10-18 Qualcomm Incorporated Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102215090A (zh) * 2010-04-02 2011-10-12 北京三星通信技术研究有限公司 一种基于mimo传输发送和接收下行控制信息的方法
CN105306114A (zh) * 2010-02-24 2016-02-03 三星电子株式会社 基站

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105306114A (zh) * 2010-02-24 2016-02-03 三星电子株式会社 基站
CN102215090A (zh) * 2010-04-02 2011-10-12 北京三星通信技术研究有限公司 一种基于mimo传输发送和接收下行控制信息的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Scheduling of multiple DL/UL transport blocks", R1-1812905, 3GPP TSG RAN WG1 MEETING #95, 2 November 2018 (2018-11-02), XP051479154 *
QUALCOMM INCORPORATED: "Scheduling of multiple DL/UL transport blocks", R1-1813040，3GPP TSG RAN WG1 MEETING #95, 3 November 2018 (2018-11-03), XP051479306 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4039028A4 (fr) * 2019-10-04 2023-10-18 Qualcomm Incorporated Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport
CN112514316A (zh) * 2020-10-14 2021-03-16 北京小米移动软件有限公司 联合调度多个传输块的方法、装置、通信设备及存储介质
CN112514316B (zh) * 2020-10-14 2023-08-15 北京小米移动软件有限公司 联合调度多个传输块的方法、装置、通信设备及存储介质

Similar Documents

Publication Publication Date Title
US11930507B2 (en) Acknowledgement feedback in in unlicensed new radio
EP3791524B1 (fr) Indication de facteur d'évolutivité de taille de bloc de transport pour une communication ultra-fiable à faible latence
US11212034B2 (en) Techniques for signaling QoS class indicators
US11140575B2 (en) Modifying CSI transmissions over uplink shared resources
US11184106B2 (en) Modulation table determination and channel quality indicator reporting
WO2020168119A1 (fr) Commutation dynamique entre différents schémas de points d'émission/réception
US11050523B2 (en) Techniques to interpret control information based on a repetition factor
US10980044B2 (en) Rate matching and semi persistent scheduling configuration in wireless communications
US11438917B2 (en) Uplink control channel resource allocation for new radio (NR)
US11374677B2 (en) Signaling of higher modulation order baseband capability
US11589372B2 (en) Handling collisions between uplink data repetitions and an uplink control transmission
EP3925091A1 (fr) Rétroaction de bande passante partielle pour livre de code de combinaison de faisceau
US10985878B2 (en) Transport block size, soft channel bit buffer size, and rate matching for short transmission time intervals
WO2020043137A1 (fr) Conception avec multiples informations de commande de liaison descendante pour nœuds émetteurs-récepteurs multiples
WO2020042016A1 (fr) Conception d'informations de commande de liaison descendante à une seule et plusieurs phases pour de multiples nœuds émetteurs-récepteurs
WO2020118632A1 (fr) Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport
WO2021012247A1 (fr) Annulation de préemption de liaison montante avec des répétitions de canal partagé de liaison montante
US11711842B2 (en) Aggregation factor associations in uplink and downlink transmissions

Legal Events

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

Ref document number: 18942848

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18942848

Country of ref document: EP

Kind code of ref document: A1