EP4039028A1 - Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport - Google Patents

Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport

Info

Publication number
EP4039028A1
EP4039028A1 EP19948031.0A EP19948031A EP4039028A1 EP 4039028 A1 EP4039028 A1 EP 4039028A1 EP 19948031 A EP19948031 A EP 19948031A EP 4039028 A1 EP4039028 A1 EP 4039028A1
Authority
EP
European Patent Office
Prior art keywords
control information
downlink control
transport blocks
encoding scheme
identifying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP19948031.0A
Other languages
German (de)
English (en)
Other versions
EP4039028A4 (fr
Inventor
Ayan SENGUPTA
Chao Wei
Alberto Rico Alvarino
Le LIU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Inc filed Critical Qualcomm Inc
Publication of EP4039028A1 publication Critical patent/EP4039028A1/fr
Publication of EP4039028A4 publication Critical patent/EP4039028A4/fr
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0045—Arrangements at the receiver end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • 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

Definitions

  • the following relates generally to wireless communications and more specifically to downlink control information for scheduling one or more transport blocks.
  • 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 one or more base stations or one or more network access nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • UE user equipment
  • Downlink control information may be used to schedule transport blocks for uplink communications or downlink communications. Signaling efficiency and overhead can be improved by controlling the amount of information in the downlink control information.
  • the described techniques relate to improved methods, systems, devices, and apparatuses that support downlink control information for scheduling one or more transport blocks.
  • the described techniques provide for encoding or decoding downlink control information (DCI) based on the number of transport blocks being scheduled by the DCI.
  • the number of transport blocks supported by the DCI may be indicated explicitly using a field included in the DCI.
  • the number of transport blocks can be implicitly signaled in a bitstream of the DCI block.
  • the type of encoding scheme may be based on the coverage enhancement (CE) mode associated with a user equipment (UE) .
  • CE coverage enhancement
  • UE user equipment
  • a method for wireless communications at a UE may include receiving a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE, identifying an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks, decoding the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme, and receiving the one or more transport blocks from a base station based on the downlink control 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 a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE, identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks, decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme, and receive the one or more transport blocks from a base station based on the downlink control information.
  • the apparatus may include means for receiving a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE, means for identifying an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks, means for decoding the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme, and means for receiving the one or more transport blocks from a base station based on the downlink control information.
  • a non-transitory computer-readable medium storing code for wireless communications at a UE is described.
  • the code may include instructions executable by a processor to receive a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE, identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks, decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme, and receive the one or more transport blocks from a base station based on the downlink control information.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the numerical quantity of the one or more transport blocks associated with the downlink control information block, where identifying the encoding scheme may be based on determining the numerical quantity.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a set of transport blocks including one or more numerical quantities of transport blocks associated with the downlink control information block, where identifying the encoding scheme may be based on determining the set of 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 field of the downlink control information block that indicates the encoding scheme, where identifying the encoding scheme may be based on the field.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining the encoding scheme or the numerical quantity implicitly from the downlink control information block for indicating one or more configurations about the one or more transport blocks, where identifying the numerical quantity may be based on determining the encoding scheme from the downlink control information block.
  • the downlink control information block uniquely determines the numerical quantity of transport blocks.
  • the one or more fields of the downlink control information for determining the encoding scheme may be jointly decoded according to the encoding scheme, where each possible output of the encoding scheme corresponds to a jointly valid combination of the one or more fields.
  • 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 coverage enhancement mode of the UE, where decoding the downlink control information block to obtain the downlink control information may be based on the coverage enhancement mode of the UE.
  • 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 redundancy version for the one or more transport blocks indicated in the downlink control information based on the identified encoding scheme, where receiving the one or more transport blocks may be based on identifying the redundancy version.
  • the redundancy version indicated in the downlink control information includes a common redundancy version for the one or more transport blocks based on the numerical quantity.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the downlink control information does not include a field to indicate the redundancy version based on the encoding scheme, where identifying the redundancy version includes identifying a default redundancy version.
  • 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 field of the downlink control information to indicate a frequency hopping configuration for the one or more transport blocks based on the encoding scheme, where receiving the one or more transport blocks may be based on the frequency hopping configuration indicated by the downlink control information.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the downlink control information does not include a field to indicate a frequency hopping configuration for the one or more transport blocks based at least in part on the encoding scheme, and identifying the frequency hopping configuration for the one or more transport blocks based at least in part on a radio resource configuration of the UE, where receiving the one or more transport blocks is based at least in part on identifying the redundancy version.
  • 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 second numerical quantity of bits of the downlink control information for indicating a modulation and coding scheme of the one or more transport blocks based on the encoding scheme associated with the downlink control information block, and identifying the modulation and coding scheme of the one or more transport blocks based on the second numerical quantity of bits, where receiving the one or more transport blocks may be based on identifying the modulation and coding scheme.
  • a range of possible modulation and coding scheme configurations associated with the one or more transport blocks may be based on the second numerical quantity of bits of the downlink control information for indicating the modulation and coding scheme.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one or more hybrid automatic repeat request processes associated with the one or more transport blocks based on a combinatorial number indicated by the downlink control information, the combinatorial number indicating a single combination of the one or more hybrid automatic repeat request processes with the encoding scheme.
  • At least one field of the downlink control information block may be jointly decoded according to the encoding scheme, where each possible output of the encoding scheme corresponds to a jointly valid combination of at least two parameters.
  • jointly decoding the at least one field of the downlink control information block is independent of the numerical quantity of the 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 decoding, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a hybrid automatic repeat request configuration and a second parameter indicating a new data indicator, where decoding the downlink control information block may be based on decoding the field.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for decoding, jointly accordingly to the encoding scheme, a field to identify a first parameter indicating a modulation and coding scheme configuration and a second parameter indicating a repetition number, where decoding the downlink control information block may be based on decoding the field.
  • the at least one field of the downlink control information block that may be jointly decoded includes a combinatorial index mapping for at least two parameters associated with the one or more transport blocks.
  • jointly decoding the at least one field of the downlink control information block is independent of the numerical quantity of the 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 applying the at least one field of the downlink control information block that may be jointly decoded to a combinatorial algorithm to determine a first configuration and a second configuration indicated by the at least one field.
  • 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 value of a field of the downlink control information block that indicates the numerical quantity of the one or more transport blocks scheduled by the downlink control information, where identifying the encoding scheme may be based on identifying the value of the field.
  • the field may be different lengths for different numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a prefix-free encoded value for a first portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information, and the field includes a non-prefix-free encoded value for a second portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that the value of the field includes a non-prefix-free encoding value, and identifying a value of one or more bits outside of the field based on identifying that the value of the field includes the non-prefix-free encoding value, where identifying the encoding scheme may be based on identifying the value of the one or more bits outside of the field.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that a first bit of the value of the field includes a first value, where identifying that the value of the field includes the non-prefix-free encoding value based on identifying that the first bit of the value of the field includes the first value.
  • the one or more bits may be part of a field indicating a hybrid automatic repeat request configuration.
  • a method for wireless communications at a base station may include determining a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information, selecting an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information, encoding the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme, transmitting, to the UE, the downlink control information block for the one or more transport blocks to the UE, and transmitting the one or more transport blocks to the UE based on the downlink control 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 determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information, select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information, encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme, transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE, and transmit the one or more transport blocks to the UE based on the downlink control information.
  • the apparatus may include means for determining a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information, means for selecting an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information, means for encoding the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme, means for transmitting, to the UE, the downlink control information block for the one or more transport blocks to the UE, and means for transmitting the one or more transport blocks to the UE based on the downlink control information.
  • a non-transitory computer-readable medium storing code for wireless communications at a base station is described.
  • the code may include instructions executable by a processor to determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information, select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information, encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme, transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE, and transmit the one or more transport blocks to the UE based on the downlink control information.
  • 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 value of a field of the downlink control information for indicating the numerical quantity, where encoding the downlink control information into the downlink control information block may be based on identifying the value.
  • the field may be different lengths for different numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a prefix-free encoded value for a first portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information, and the field includes a non-prefix-free encoded value for a second portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying that the value of the field includes a non-prefix-free encoding value, and shifting a value of a parameter indicating a hybrid automatic repeat request configuration based on identifying that the value of the field includes a non-prefix-encoding value, where selecting the encoding scheme may be based on shifting the value of the parameter.
  • 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 value for one or more fields of the downlink control information for indicating one or more configurations about the one or more transport blocks based on the numerical quantity and one or more desired configurations of the one or more transport blocks, where encoding the downlink control information into the downlink control information block may be based on identifying the value.
  • 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 coverage enhancement mode associated with the UE, where selecting the encoding scheme for the downlink control information may be based on the coverage enhancement mode associated with the UE.
  • 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 redundancy version for the one or more transport blocks to indicate in the downlink control information based on the numerical quantity of the one or more transport blocks, where encoding the downlink control information may be based on identifying the redundancy version.
  • the redundancy version indicated in the downlink control information includes a common redundancy version for the one or more transport blocks based on the numerical quantity.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for omitting an indicator of a redundancy version from the downlink control information based on the numerical quantity, where encoding the downlink control information may be based on omitting the indicator of the redundancy version from the downlink control information.
  • 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 field of the downlink control information to indicate a frequency hopping configuration for the one or more transport blocks based on the numerical quantity of the one or more transport blocks, where encoding the downlink control information may be based on the frequency hopping configuration.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for omitting an indicator of a frequency hopping configuration from the downlink control information based at least in part on the numerical quantity, where encoding the downlink control information is based at least in part on omitting the indicator of the frequency hopping configuration from the downlink control information.
  • 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 second numerical quantity of bits of the downlink control information for indicating a modulation and coding scheme of the one or more transport blocks based on the numerical quantity of the one or more transport blocks associated with the downlink control information, where encoding the downlink control information may be based on identifying the second numerical quantity of bits of the downlink control information for indicating the modulation and coding scheme.
  • 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 range of possible modulation and scheme configurations associated with the one or more transport blocks, where identifying the second numerical quantity of bits may be based on identifying the range of possible modulation and coding scheme configurations.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for assigning a unique combinatorial number to each possible combination of hybrid automatic repeat request processes with the numerical quantity of the one or more transport blocks associated with the downlink control information, where the downlink control information includes the unique combinatorial number.
  • At least one field of the downlink control information block may be jointly encoded according to the encoding scheme to include values for at least two parameters, where each possible output of the encoding scheme corresponds to a jointly valid combination of the at least two parameters.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for encoding, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a hybrid automatic repeat request configuration and a second parameter indicating a new data indicator, where encoding the downlink control information block may be based on encoding the field.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for encoding, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a modulation and coding scheme configuration and a second parameter indicating a repetition number, where encoding the downlink control information block may be based on encoding the field.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a combinatorial index mapping for the at least two parameters of the one or more transport blocks, where the at least one field of the downlink control information block that may be jointly encoded includes the combinatorial index mapping.
  • Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for applying a first parameter and a second parameter to a combinatorial algorithm to determine a combinatorial index mapping for the at least one field of the downlink control information block that may be jointly encoded.
  • FIG. 1 illustrates an example of a system for wireless communications that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 2 illustrates an example of a wireless communications system that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 3 illustrates an example of a process flow that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 4 illustrates an example of a encoding scheme that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 5 and 6 show diagrams of devices that support downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 7 shows a diagram of a communication manager that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 8 shows a diagram of a system including a device that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 9 and 10 show diagrams of devices that support downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 11 shows a diagram of a communication manager that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIG. 12 shows a diagram of a system including a device that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • FIGs. 13 through 16 show flowcharts illustrating methods that support downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • Downlink control information may be used to schedule one or more transport blocks. As the number of transport blocks scheduled by a DCI increases, so can the size of the DCI. Encoding/decoding techniques may be implemented to limit the size of the DCI even as the number of transport blocks scheduled by the DCI increases.
  • a first encoding scheme may be used to encode/decode the DCI.
  • a second encoding scheme may be used to encode/decode the DCI.
  • the number of transport blocks may be indicated explicitly using a dedicated field included in the DCI. In other examples, the number of transport blocks can be implicitly signaled in the bitstream of the DCI block.
  • the type of encoding scheme may be based on the coverage enhancement (CE) mode associated with the UE. For example, if the UE is in CE Mode A, a first set of encoding schemes may be available to encode/decode the DCI based on the different numbers of transport blocks. If the UE is in CE Mode B, a second set of encoding schemes may be available to encode/decode the DCI based on the different numbers of transport blocks.
  • CE coverage enhancement
  • aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are described with reference to a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to downlink control information for scheduling one or more transport blocks.
  • FIG. 1 illustrates an example of a wireless communications system 100 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more base stations 105, one or more 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-A Pro
  • NR New Radio
  • the wireless communications system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.
  • ultra-reliable e.g., mission critical
  • the base stations 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may be devices in different forms or having different capabilities.
  • the base stations 105 and the UEs 115 may wirelessly communicate via one or more communication links 125.
  • Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base station 105 may establish one or more communication links 125.
  • the coverage area 110 may be an example of a geographic area over which a base station 105 and a UE 115 may support the communication of signals according to one or more radio access technologies.
  • the UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times.
  • the UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1.
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115, the base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) , as shown in FIG. 1.
  • network equipment e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment
  • the base stations 105 may communicate with the core network 130, or with one another, or both.
  • the base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via an S1, N2, N3, or other interface) .
  • the base stations 105 may communicate with one another over the backhaul links 120 (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) , or both.
  • the backhaul links 120 may be or include one or more wireless links.
  • One or more of the base stations 105 described herein may include or may be referred to by a person having ordinary skill 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 a giga-NodeB (either of which may be referred to as a gNB) , a Home NodeB, a Home eNodeB, or other suitable terminology.
  • a base transceiver station a radio base station
  • an access point a radio transceiver
  • a NodeB an eNodeB (eNB)
  • eNB eNodeB
  • a next-generation NodeB or a giga-NodeB either of which may be referred to as a gNB
  • gNB giga-NodeB
  • a UE 115 may include or may 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, among other examples.
  • a UE 115 may also include or may be referred to as 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 include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
  • WLL wireless local loop
  • IoT Internet of Things
  • IoE Internet of Everything
  • MTC machine type communications
  • the UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • devices such as other UEs 115 that may sometimes act as relays as well as the base stations 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
  • the UEs 115 and the base stations 105 may wirelessly communicate with one another via one or more communication links 125 over one or more carriers.
  • the term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links 125.
  • a carrier used for a communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) .
  • BWP bandwidth part
  • Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling.
  • the wireless communications system 100 may support communication with a UE 115 using 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 frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.
  • FDD frequency division duplexing
  • TDD time division duplexing
  • Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (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
  • a resource element may consist of 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 coding rate of the modulation scheme, or both) .
  • 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 or beams) , and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE 115.
  • Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) .
  • Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
  • SFN system frame number
  • Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration.
  • a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots.
  • each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing.
  • Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) .
  • a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
  • a subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) .
  • TTI duration e.g., the number of symbol periods in a TTI
  • the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
  • 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 one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques.
  • a control region e.g., a control resource set (CORESET)
  • CORESET control resource set
  • a control region for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier.
  • One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115.
  • one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner.
  • An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size.
  • Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
  • 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, but the different geographic coverage areas 110 may be supported by the same base station 105.
  • the overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105.
  • the wireless communications system 100 may include, for example, a heterogeneous network in which different types of the base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.
  • the wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof.
  • the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications.
  • the UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions) .
  • Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT) , mission critical video (MCVideo) , or mission critical data (MCData) .
  • MCPTT mission critical push-to-talk
  • MCVideo mission critical video
  • MCData mission critical data
  • Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications.
  • the terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.
  • a UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol) .
  • D2D device-to-device
  • P2P peer-to-peer
  • One or more 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 the 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. In other cases, D2D communications are carried out between the UEs 115 without the involvement of a base station 105.
  • 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) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function
  • S-GW serving gateway
  • PDN Packet Data Network gateway
  • UPF user plane function
  • the control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the base stations 105 associated with the core network 130.
  • NAS non-access stratum
  • User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions.
  • the user plane entity may be connected to the network operators IP services 150.
  • the operators IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
  • Some of the network devices may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC) .
  • Each access network entity 140 may communicate with the UEs 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs) .
  • Each access network transmission entity 145 may include one or more antenna panels.
  • various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station 105) .
  • the 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 because the wavelengths range from approximately one decimeter to one meter in length.
  • UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors.
  • the transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) 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
  • the wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands.
  • the 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 industrial, scientific, and medical (ISM) band.
  • LAA License Assisted Access
  • LTE-U LTE-Unlicensed
  • NR NR technology
  • an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band.
  • devices such as the base stations 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance.
  • 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, P2P transmissions, or D2D transmissions, among other examples.
  • a base station 105 or a 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.
  • the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, 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.
  • an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.
  • 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, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a 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 some 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 amplitude offsets, phase offsets, or both to signals carried via 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) .
  • the UEs 115 and the base stations 105 may support retransmissions of data to increase the likelihood that data is received successfully.
  • Hybrid automatic repeat request (HARQ) feedback is one technique for 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 medium access control (MAC) layer in poor radio conditions (e.g., low signal-to-noise conditions) .
  • MAC medium access control
  • a 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.
  • 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 multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • a wireless network for example a wireless local area network (WLAN) , such as a Wi-Fi (i.e., Institute of Electrical and Electronics Engineers (IEEE) 802.11) network may include an access point (AP) that may communicate with one or more wireless or mobile devices.
  • the AP may be coupled to a network, such as the Internet, and may enable a mobile device to communicate via the network (or communicate with other devices coupled to the access point) .
  • a wireless device may communicate with a network device bi-directionally.
  • a device may communicate with an associated AP via downlink (e.g., the communication link from the AP to the device) and uplink (e.g., the communication link from the device to the AP) .
  • a wireless personal area network which may include a Bluetooth connection, may provide for short range wireless connections between two or more paired wireless devices.
  • wireless devices such as cellular phones may utilize wireless PAN communications to exchange information such as audio signals with wireless headsets.
  • the number of transport blocks supported by the DCI may be indicated explicitly using a field included in the DCI.
  • the number of transport blocks can be implicitly signaled in a bitstream of the DCI block.
  • the type of encoding scheme may be based on the CE mode associated with the UE.
  • wireless communications system 100 may more efficiently communicate parameters for one or more transport blocks scheduled by a DCI. Such features may improve signaling efficiency by reducing an amount of control information communicated relative to data being communicated. In some examples, reducing the size of DCI transmitted may improve the coverage area that can effectively receive the DCI. In some examples, reducing the size of DCI transmitted may reduce the power consumption of the UE 115 when transmitting the DCI. By compressing the DCI and using the DCI to schedule one or more transport blocks, the user experience with the UE 115 may improve by improving the battery life, improving data throughput, and decreasing a likelihood that data is lost.
  • FIG. 2 illustrates an example of a wireless communications system 200 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the wireless communications system 200 may implement aspects of wireless communication system 100.
  • Wireless communications system 200 may include UE 115-a and base station 105-a, which may be examples of a UE 115 and a base station 105 described with reference to FIG 1.
  • Base station 105-a and UE 115-a may communicate using a downlink link 205 and an uplink link 210.
  • Base station 105-a may transmit DCI to UE 115-a on the downlink link 205 to schedule transmissions.
  • the DCI may schedule resources for base station 105-a to transmit a transport block 220 on the downlink link 205 to UE 115-a for downlink communications.
  • the DCI may schedule UE 115-a to transmit a transport block 220 on the uplink link 210 to base station 105-a for uplink communications.
  • the transport block 220 may carry uplink or downlink data and be transmitted on an uplink data channel (e.g., a physical uplink shared channel (PUSCH) ) or a downlink data channel (e.g., a physical downlink shared channel (PDSCH) ) scheduled by the DCI.
  • an uplink data channel e.g., a physical uplink shared channel (PUSCH)
  • a downlink data channel e.g., a physical downlink shared channel (PDSCH) scheduled by the DCI.
  • PUSCH physical uplink shared channel
  • PDSCH physical downlink shared channel
  • a single DCI transmission may schedule a single transport block.
  • the base station 105 may transmit a DCI for each of the pending transport blocks. This may result in high power consumption for the UE 115, as the UE 115 may monitor for each of the DCI individually and decode them in order to receive the scheduling for the transport blocks.
  • the base station 105-a may instead transmit a DCI block 215 to schedule one or more transport blocks 220.
  • a DCI block 215 may be configurable to support any number of transport blocks 220 (e.g., one, two, three, four, five, six, seven, eight, etc. ) .
  • the DCI block 215 may include control information for each of the one or more transport blocks 220.
  • the DCI block 215 may schedule a first transport block 220-a (TB1) , a second transport block 220-b (TB2) , and a third transport block 220-c (TB3) as well as other transport blocks 220 not shown.
  • the DCI block 215 may schedule fewer transport blocks 220 than what is shown.
  • the DCI block 215 may schedule between 1 and N transport blocks 220, where N may be an integer such as one, two, three, four, five, six, seven, eight, etc. In some cases, N transport blocks 220 may be 2, 4, 8, and so on (e.g., where N is a power of 2, or 2 n ) .
  • the value of N may be configurable and may be based on, for example, a type of communications between base station 105-a and UE 115-a. For example, N may be based on whether the communications are machine type communications (MTC) or a coverage enhancement mode for MTC, whether the communications are IoT (e.g., narrowband (NB) IOT) , etc. Techniques described herein may be applied for encoding DCI based on a numerical quantity of transport blocks supported by the DCI.
  • MTC machine type communications
  • NB narrowband
  • the size of the DCI to communicate parameters about each transport block may increase.
  • Parameter about transport blocks that are communicated by DCI may include HARQ process configurations, new data indicators (NDIs) , modulation and coding scheme (MCS) configurations, repetition number configurations, redundancy version configurations, frequency hopping indications, or combinations thereof.
  • NDIs new data indicators
  • MCS modulation and coding scheme
  • repetition number configurations repetition number configurations
  • redundancy version configurations frequency hopping indications, or combinations thereof.
  • PDCCH physical downlink control channel
  • the DCI may be compressed by jointly encoding parameters into a single field.
  • the DCI may be encoded to form a DCI block.
  • the DCI block may be a compressed form of the underlying DCI.
  • the terms DCI and DCI block may be used interchangeable throughout this disclosure.
  • the encoding scheme may omit invalid combinations of the parameter configurations to ensure that every value of the jointly encoded field indicates a valid combination of parameter configurations. For example, if HARQ processes and NDI are jointly encoded in a single field of the DCI block, and a HARQ process is not scheduled, an NDI also does not need to be scheduled. Thus, a combination that does not schedule a HARQ process for a transport block and schedules an NDI for that same transport block may be an invalid combination that the encoding scheme is configured to omit.
  • some parameters may be common across all N transport blocks that may be scheduled by the DCI.
  • the HARQ processes scheduled, corresponding NDIs, and potentially, corresponding redundancy version indices may be jointly encoded into a single field to eliminate signaling redundant combinations across these parameters.
  • the MCS and repetition number may be jointly encoded to save the total number of combinations needed to be signaled. This may occur because when the number of repetitions configured for PDSCH/PUSCH is large, the coverage is most likely poor, resulting in some MCS configurations (e.g., large MCS values) being of limited usefulness.
  • the number of repetitions of PDSCH/PUSCH and the frequency hopping (FH) indicator may be jointly encoded to limit the size of the resulting DCI block that is communicated to the UE 115-a.
  • the FH indicator may be redundant.
  • the number of valid combinations of the number of repetitions and the frequency hopping indicator may be less than a total number of possible combinations for CE Mode A.
  • An upper limit of the numerical quantity of transport blocks that can be scheduled by a DCI may depend on the CE Mode of the communications with the UE. For example, if the CE Mode A is employed, the upper limit of the number of transport blocks that can be scheduled by a DCI may be eight (8) . In another example, if the CE Mode B is employed, the upper limit of the number of transport blocks that can be scheduled by a DCI may be four (4) .
  • the size of the DCI block may be independent from the numerical quantity of transport blocks scheduled by the DCI block.
  • the DCI block may be a first size whether one transport block is scheduled or whether eight transport blocks are scheduled.
  • the information communicated in DCI for higher numerical quantities of transport blocks may be compressed to fit more information into the DCI block .
  • the DCI block may be encoded with a first encoding scheme that provides full scheduling flexibility. If more transport blocks are being scheduled by the DCI (e.g., three or more transport blocks) , the DCI block may be encoded with a second encoding scheme different than the first encoding scheme that provides reduced scheduling flexibility.
  • the reduced scheduling flexibility may occur certain parameters may be jointly encoded into a single field.
  • the MCS and the repetition number may be jointly encoded, where in the first encoding scheme those parameters are communicated in their own fields.
  • the encoding scheme and the resultant interpretation of the fields of the DCI block may be based on the number of transport blocks scheduled by the DCI block.
  • a simple example of such a partition is two sets that include a first set of one and two transport blocks being supported (e.g., ⁇ 1, 2 ⁇ ) and a second set of three or more transport blocks being supported (e.g., ⁇ 3, N ⁇ ) . Any number of sets and divisions of sets may be supported.
  • Each set of transport blocks may be associated with a unique encoding scheme.
  • a base station 105-a may identify the number of transport blocks to be scheduled by a DCI and then identify an encoding scheme for encoding the DCI into a DCI block based on the set divisions described herein.
  • the UE 115-b may identify the number of transport blocks scheduled by the DCI block or the encoding scheme used to encode the DCI block based on the information in the DCI block and then apply a corresponding decoder.
  • Partitioned sets of transport blocks may include any number of transport blocks, including one, two, three, four, five, six, seven, or eight transport blocks.
  • the DCI block may be configured to include an explicit indication of the numerical quantity of transport blocks scheduled by the DCI.
  • the DCI block may include a field configured to indicate the number of transport blocks scheduled.
  • the field may be configured to indicate which set of transport blocks are supported.
  • the field may be configured to indicate which encoding scheme was used to encode the transport block.
  • the DCI block may include a 1-bit field to indicate which set or which encoding scheme is used.
  • the field for explicitly indicating the number of transport blocks scheduled by the DCI block, the set of transport blocks scheduled by the DCI block, or the encoding scheme used to encode the DCI block may be any number of bits (e.g., one, two, three, four, five, six, etc. )
  • the DCI block may be configured to implicitly indicate the numerical quantity of transport blocks scheduled by the DCI block.
  • the UE 115-a may be configured to identify the numerical quantity of based on the values of one or more other fields of the DCI block. In some cases, it may be based on fields that jointly encode two or more parameters. For example, a field used to indicate a configuration of a parameter (e.g., such as MCS or repetition number) may be jointly encoded with an indication of the numerical quantity of transport blocks supported by the DCI block. In some examples, a field used to indicate jointly encoded parameters may be further configured to indicate three or more parameters, including the numerical quantity of transport blocks supported by the DCI block.
  • the UE 115-a may expect values within 0-31 for first section of bits of the DCI block (e.g., a bitstream a 2 ...a 6 of the DCI block) . If the value represented by the first section is between 0-7, the UE 115-a may determine that one transport block is being scheduled by the DCI, while if the value represented by the first section is between rom 8-31, the UE 115-a may determine that two transport blocks are scheduled. So, the UE 115-a may read the bitstream, and based on criterion, know which encoding/decoding algorithm to apply. In some cases, every event scheduled by the DCI corresponds to a unique number/bitstream.
  • Some parameters indicated by fields in the DCI block may be encoded/decoded differently based on the numerical quantity of transport blocks being scheduled by the DCI.
  • Examples of parameters that may be encoded/decoded differently based on the numerical quantity of the transport blocks include a redundancy version for the transport blocks, a frequency hopping indication, an MCS configuration, or a combination thereof.
  • one or more redundancy versions for the transport blocks may be encoded/decoded differently in the DCI block based on the numerical quantity of the transport blocks. For example, when a certain number of transport blocks (e.g., one transport block or two transport blocks) is scheduled, the redundancy version for those one or more transport blocks may be signaled in the DCI; while for other numbers of transport blocks (e.g., three or more transport blocks) scheduled, the DCI may signal a common redundancy version field for all the transport blocks scheduled or, alternatively, not signal a redundancy version for the transport blocks scheduled by the DCI.
  • the redundancy version for those one or more transport blocks may be signaled in the DCI; while for other numbers of transport blocks (e.g., three or more transport blocks) scheduled, the DCI may signal a common redundancy version field for all the transport blocks scheduled or, alternatively, not signal a redundancy version for the transport blocks scheduled by the DCI.
  • the UE 115-a may determine that the redundancy version is a default redundancy version for the one or more transport blocks or a default set of redundancy versions for the one or more transport blocks.
  • the redundancy version for the one or more transport blocks may be omitted from the DCI. Such an omission may be based on the numerical of transport blocks scheduled by the DCI.
  • the UE 115-a may determine whether a redundancy version is enabled or may determine a redundancy version configuration based on an RRC configuration of the UE 115-a. These instances of indicating the one or more redundancy versions may be employed in any coverage enhancement mode (e.g., CE Mode A or CE Mode B) .
  • the frequency hopping indicator for the transport blocks may be encoded/decoded differently in the DCI block based on the numerical quantity of the transport blocks. For example, when a certain number of transport blocks (e.g., one transport block or two transport blocks) is scheduled, the DCI may include a field that indicates frequency hopping parameter; while for other numbers of transport blocks (e.g., three or more transport blocks) scheduled, the DCI may not include the field that indicates the frequency hopping parameter. In instances where the field for frequency hopping is not included in the DCI, the frequency hopping configuration may be based on information included in the system information block (SIB) . These instances of indicating the frequency hopping parameter may be employed in any coverage enhancement mode (e.g., CE Mode A or CE Mode B) .
  • SIB system information block
  • the frequency hopping indicator for the one or more transport blocks may be omitted from the DCI. Such an omission may be based on the numerical of transport blocks scheduled by the DCI.
  • the UE 115-a may determine whether frequency hopping is enabled or may determine a frequency hopping configuration based on an RRC configuration of the UE 115-a.
  • one or more MCS configurations for the transport blocks may be encoded/decoded differently in the DCI block based on the numerical quantity of the transport blocks. For example, when a certain number of transport blocks (e.g., one transport block or two transport blocks) is scheduled, full MCS scheduling flexibility may be utilized afforded; while for other numbers of transport blocks (e.g., three or more transport blocks) scheduled, the numerical quantity of possible MCS configurations that may be indicated by the DCI may be restricted. In some instances (described in more detail herein) , the numerical quantity of possible MCS configuration that may be indicated by the DCI may be based on the number of the bits in the field that indicates the number of repetitions.
  • the MCS configurations indicated by the MCS field of the DCI may use a distinct interpretation of the MCS tables used in legacy DCI.
  • the MCS values indicated in the DCI may point to the lowest MCS values in the MCS tables or may point to some subset of the MCS values in the MCS tables.
  • These instances of indicating the one or more MCS configurations may be employed in any coverage enhancement mode (e.g., CE Mode A or CE Mode B) .
  • Some parameters may be encoded in the DCI block the same way, regardless of how many transport blocks are scheduled by the DCI.
  • the HARQ process identifiers scheduled by the DCI and the corresponding NDIs may be jointly encoded in the same field of the DCI block in every encoding scheme, irrespective of the numerical quantity of transport blocks scheduled by the DCI block.
  • one or more HARQ processes for the transport blocks may be encoded/decoded differently in the DCI block based on the numerical quantity of the transport blocks.
  • the encoding scheme may be based upon assigning a unique combinatorial number r k to each possible combination of HARQ processes with k transport blocks (out of a possible N transport blocks) scheduled, such that the UE 115-a can determine the exact k-combination from r k . Additional or alternatively, uniquely identifiable combinatorial numbers corresponding to the HARQ processes scheduled may be used as part of the encoding process.
  • the uniquely identifiable combinatorial numbers may correspond to the NDIs of the HARQ processes scheduled, the redundancy version indices (when signaled) of the HARQ processes scheduled, or combinations thereof.
  • One or more uniquely identifiable combinatorial numbers corresponding to the jointly-encoded identities of the HARQ processes scheduled, the NDIs, the redundancy version indices (when signaled) , or combinations thereof may be employed in the DCI encoding. These instances of indicating the one or more HARQ processes may be employed in any coverage enhancement mode (e.g., CE Mode A or CE Mode B) .
  • a first detailed example of a DCI encoding/decoding scheme to support one or more transport blocks scheduled by the DCI is described. This first detailed example may be implemented in any CE mode or may be modified based on any of the techniques and options described herein. Specific values should not be considered limiting to this disclosure.
  • the DCI block may be first number of bits that is fixed, irrespective of how many transport blocks are scheduled by the DCI.
  • the DCI block may be 13-bits.
  • the DCI block may include the following a fields: a first field to indicate the encoding scheme used to encode the DCI block (or the number of transport blocks supported) , a second field that is jointly encoded to indicate the HARQ process and the NDI, a third field to indicate MCS configurations, a fourth filed to indicate repetition numbers, or a combination thereof.
  • the third field may be jointly encoded to indicate the MCS configurations and the repetitions numbers and no fourth field may be included.
  • a first bit a 1 of the DCI block may indicate the encoding scheme used or the number of transport blocks scheduled.
  • the first bit may be a zero (0) if the first encoding scheme is used or may be a one (1) if the second encoding scheme is used.
  • additional bits may be used to indicate this value.
  • Bits a 2 through a 6 may represent a jointly encoded value of a HARQ parameter and NDI.
  • these bits may represent up to 32 valid combinations of the HARQ process and NDI parameters (e.g., ) , when a single transport block is supported. If a different number of transport blocks are supported (e.g., two transport blocks are supported) the number of valid combinations may be different.
  • the combinatorial index value of these bits may be determined a first encoding algorithm described in more detail below.
  • Bits a 7 through a 10 may indicate one or more MCS configurations for the one or more transport blocks.
  • Bits a 11 through a 13 may indicate one or more repetition numbers for the one or more transport blocks.
  • a first bit a 1 of the DCI block may indicate the encoding scheme used or the number of transport blocks scheduled.
  • the first bit may be a one (1) indicating that the second encoding scheme is used.
  • Bits a 2 through a 7 may represent a jointly encoded value of a HARQ parameter and NDI. In some examples, these bits may represent up to 48 valid combinations of the HARQ process and NDI parameters (e.g., ) ) , when a three transport blocks are supported.
  • bits a 8 through a 13 may represent a jointly encoded value to indicate one or more MCS configurations for the one or more transport blocks and one or more repetition numbers for the one or more transport blocks.
  • the jointly encoded value for these bits may be determined based on the table provided below.
  • Table 1 Bits a 8 through a 13 for the second encoding scheme
  • the number of bits in the jointly encoded value for the MCS configuration may be based on the repetition number being signaled.
  • the range of possible MCS configurations available may be based on the repetition number. For example, if a first repetition number is used, up to sixteen (16) unique MCS configurations may be encoded in the DCI block. In contrast, if a different repetition number is used, up to four (4) unique MCS configurations may be encoded.
  • the base station 105-a may identify a range possible MCS configurations before encoding the DCI block. When using a reduced range of possible MCS values, the base station 105-a may identify a subset of the MCS tables from which the base station 105-a may select the encoded MCS configuration.
  • the subset of MCS values from which the base station 105-a may select may be the lowest MCSs in the MCS tables.
  • any subset the MCS values in the MCS tables may be defined for any granularity of MCS signaling the DCI block.
  • one or more mapping tables may map indices of the subset to the indices of the underlying MCS tables.
  • Equation 2 The term is a combinatorial index mapping the NDIs of the HARQ processes scheduled above, and is given by Equation 2.
  • bits a 2 through a 6 may be determined using Equation 4.
  • bits a 2 through a 7 may be determined using Equation 6.
  • Jointly encoded values included in a DCI block may be determined using look-up tables of pre-defined values (e.g., Table 1) , may be determined using combinatorial algorithms (e.g., Equations 1–6) , or may be determined using a combination thereof.
  • a jointly encoded value may be an example of a combinatorial index mapping that may be decoded by the UE 115-a using look-up tables, combinatorial algorithms, or a combination thereof.
  • the base station 105-a and the UE 115-a may be configured to use algorithms rather than stored values to decode or determine the values of the parameters indicated by DCI.
  • FIG. 3 illustrates an example of a process flow 300 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the process flow 300 may implement aspects of wireless communication systems 100 or 200.
  • Process flow 300 may include UE 115-b and base station 105-b, which may be examples of a UE 115 and a base station 105 described with reference to FIGs. 1 and 2.
  • the base station 105-b When communicating DCI, the base station 105-b may be configured to compress the DCI into a DCI block based on the numerical quantity of transport blocks scheduled by the DCI.
  • the process flow 300 illustrates functions and communications of the base station 105-b and the UE 115-b to both encode a DCI block and decode the DCI block based on the numerical quantity of transport blocks being scheduled by the DCI.
  • the process flow 300 incorporates the features described with reference to FIG. 2 and any modifications of the process flow 300 based on the features described with reference to FIG. 2 are within the scope of this disclosure.
  • the base station 105-b may determine a numerical quantity of transport blocks scheduled by DCI.
  • a DCI may be configured to support any number N of transport blocks (e.g., one, two, three, four, five, six, seven, eight, etc. ) .
  • the encoding scheme used to encode a DCI block may be based on the numerical quantity of the transport blocks being scheduled by the DCI. In some cases, the encoding scheme used to encode a DCI block may also be based on a coverage enhancement mode (e.g., CE Mode A or CE Mode B) . Additional details about determining the numerical quantity of transport blocks scheduled by the DCI are described with reference to FIG. 2.
  • the base station 105-b may select an encoding scheme for the downlink control information.
  • the base station 105-b may use the encoding scheme to generate a downlink control information block 320 to communicate to the UE 115-b.
  • Selecting the encoding scheme may be based at least in part on the numerical quantity of transport blocks scheduled by the DCI, a set of numerical values of transport blocks scheduled by the DCI, a coverage enhancement mode associated with the UE 115-b, or a combination thereof.
  • the base station 105-b may identify the selected encoding scheme based on a mapping between numerical quantities of transport blocks and possible encoding schemes.
  • the base station 105-b may identify a set of transport blocks based on the numerical quantity of transport blocks scheduled by the DCI and identify the selected encoding scheme based on a mapping between the possible sets of transport blocks and the possible encoding schemes.
  • the encoding scheme may be the encoding scheme described with reference to FIG. 4 and the processes for selecting and encoding may be accomplished using the features described with reference to FIG. 4.
  • the types of encoding schemes used and the mappings between the numerical values of transport blocks (or the sets of transport blocks) may be based on the coverage enhancement mode associated with the UE 115-b. For example, different coverage enhancement modes may use the same or different encoding schemes or may use the same or different mappings between the numerical values of transport blocks (or the sets of transport blocks) and the possible encoding schemes.
  • Coverage enhancement modes associated with the UE 115-b may be established using radio resource control (RRC) signaling.
  • RRC radio resource control
  • the base station 105-b may identify the coverage enhancement mode associated with the UE 115-b and then use the encoding schemes or mappings associated with the identified coverage enhancement mode. Additional details about selecting the encoding scheme are described with reference to FIG. 2.
  • the base station 105-b may encode the downlink control information based on the encoding scheme. As a result, the base station 105-b may generate the downlink control information block 320.
  • the downlink control information block 320 may represent a compressed version of the information included in the DCI.
  • the base station 105-b may transmit the downlink control information block 320 to the UE 115-b after encoding the DCI using the encoding scheme. Additional details about encoding the downlink control information based on the encoding scheme are described with reference to FIG. 2.
  • the downlink control information block 320 may include explicit signaling of the numerical value of transport blocks scheduled by the DCI or may include implicit signaling of the numerical value of the transport blocks scheduled by the DCI. Additional details about the explicit signaling and the implicit signaling are described with reference to FIG. 2.
  • the downlink control information block 320 may include an indication of the numerical quantity of transport blocks scheduled by the DCI, a set of transport blocks scheduled by the DCI, an encoding scheme used to encode the downlink control information block 320, or a combination thereof. From any of these possible values, the UE 115-b may be configured to derive any of the other listed values.
  • the UE 115-b may identify the encoding scheme associated with the downlink control information block 320 based on receiving the downlink control information block 320 from the base station 105-b.
  • the UE 115-b may identify the encoding scheme based on explicit signaling or implicit signaling in the downlink control information block.
  • the UE 115-b may identify the encoding scheme using an indication of the numerical quantity of transport blocks scheduled by the DCI, a set of transport blocks scheduled by the DCI, an encoding scheme used to encode the downlink control information block 320, or a combination thereof.
  • the UE 115-b may identify the coverage enhancement mode associated with the UE 115-b and then use the encoding schemes or mappings associated with the identified coverage enhancement mode. Additional details about identifying the encoding scheme associated with the downlink control information block are described with reference to FIG. 2.
  • the encoding scheme may be the encoding scheme described with reference to FIG. 4 and the processes for identifying and decoding may be accomplished using the features described with reference to FIG. 4.
  • the UE 115-b may decode the downlink control information block 320 using the encoding scheme.
  • the UE 115-b may decode one or more fields of the downlink control information block 320 that are jointly encoded to identify two or more parameters indicated by the DCI. Additional details about decoding the downlink control information block using the encoding scheme are described with reference to FIG. 2.
  • the UE 115-b may receive one or more transport blocks 335 from the base station 105-b based on the DCI communicated from the base station 105-b to the UE 115-b.
  • the base station 105-b may transmit the one or more transport blocks 335 a specified duration after transmitting the downlink control information block 320.
  • FIG. 4 illustrates an example of an encoding scheme 400 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the encoding scheme 400 may implement aspects of wireless communication systems 100 or 200.
  • the encoding scheme 400 may be an example of a specific encoding scheme that can be used to encode DCI into a DCI block, where the DCI can schedule one or more transport blocks.
  • the encoding scheme 400 illustrates a DCI for scheduling up to eight (8) transport blocks.
  • the encoding scheme 400 may be for a DCI in CE Mode A.
  • the encoding scheme 400 may be for a DCI in CE Mode B.
  • the encoding scheme 400 may be modified for scheduling any numerical quantity of transport blocks.
  • the encoding scheme 400 may be used in conjunction with the features described with reference to FIGs. 2 and 3. Specifically, the features for encoding HARQ parameters, RV parameters, NDIs, or frequency hopping parameters, or combinations thereof may be used conjunction with the features of the encoding scheme 400, among other features described with reference to FIGs. 2 and 3.
  • the encoding scheme 400 may be designed to comply with some constraints. Some examples of such constraints are shown in Table 2 below.
  • the encoding scheme 400 of FIG. 4 is illustrated in a table with the columns representing bits of DCI and the rows representing the DCI encoding scheme used for a specific numerical quantity of transport blocks being scheduled by the DCI.
  • the encoding scheme 400 includes eight individual schemes 405-440 for encoding DCI being used to schedule eight different numerical quantities of transport blocks.
  • a first scheme 405 is for scheduling one transport block in the DCI.
  • a second scheme 410 is for scheduling two transport blocks in the DCI.
  • a third scheme 415 is for scheduling three transport blocks in the DCI.
  • a fourth scheme 420 is for scheduling four transport blocks in the DCI.
  • a fifth scheme 425 is for scheduling five transport blocks in the DCI.
  • a sixth scheme 430 is for scheduling six transport blocks in the DCI.
  • a seventh scheme 435 is for scheduling seven transport blocks in the DCI.
  • An eighth scheme 440 is for scheduling transport blocks in the DCI.
  • the schemes 405–440 are illustrated in a non-numerical order to illustrate features about the indicators of the numerical quantity of transport blocks encoded in the DCI.
  • the fields for indicators the indicators of the numerical quantity of transport blocks are shown in the white blocks of the encoding scheme 400.
  • the DCI may include a field that includes an indicator of the numerical quantity of transport blocks encoded in the DCI.
  • the field for each scheme 405–440 is shown in the white blocks of each scheme 405–440.
  • the field or indicator may vary in size for different numerical quantities of transport blocks being scheduled. This may be based at least in part on that different numerical quantities of transport blocks use different amounts of bits to schedule the transport blocks.
  • the fields for the first scheme 405 and the seventh scheme 435 may use five bits, while the field for the second scheme 410 may use two bits and the field for the fourth scheme 420 may use a single bit.
  • Other quantities of bits for different schemes are shown in more detail in FIG. 4. In some cases, the terms field and indicator may be used interchangeably.
  • the specific values in the indicators for each scheme 405–440 may be configured to make decoding the DCI easier.
  • the indicators may be examples of prefix-free encoding such that decoding can be accomplished using a logic tree.
  • the decoding of the indicators can be done using hardware, firmware, or software, or a combination thereof.
  • prefix-free encoding a message can be transmitted as a sequence of concatenated code words, without any out-of-band markers or, alternatively markers between words to frame the words in the message.
  • the receiver can decode the message unambiguously, by repeatedly finding and removing sequences that form valid code words.
  • the indicators of schemes 405, 415, 425, 430, 435, and 440 may be examples prefix-free encoding and the schemes 405, 415, 425, 430, 435, and 440 can be decoded unambiguously using the indicators.
  • the indicators of the schemes 410 and 420 are not examples of prefix-free encoding and the decoder (e.g., a UE or other recipient of DCI) may use additional information to distinguish between the second scheme 410 and the fourth scheme 420.
  • the first bit (b 0 ) of the DCI for prefix-free encoded indicators begins with a ‘0’ logic value and the first bit (b 0 ) of the DCI for non-prefix-free encoded indicators begins with a ‘1’ logic value.
  • the decoder may be configured to quickly determine whether additional processing is needed or if the decoding can be done using the prefix-free encoded indicator alone. In such cases, the decoder may identify that the value of the field includes a non-prefix-free encoded value based on the first bit (b 0 ) of the DCI.
  • additional bits of the DCI may be used to distinguish the schemes 410 and 420 from each other.
  • the decoder may identify a value of one or more bits outside the field that includes the indicator.
  • the decoder may evaluate the second bit (b 1 ) of the DCI. If the second bit (b 1 ) of the DCI is a ‘0’ logic value, then the DCI unambiguously is for the fourth scheme 420.
  • the second bit (b 1 ) of the DCI for the fourth scheme 420 is used to encode one or more HARQ identifiers. Thus, there are situations where the second bit (b 1 ) of the DCI can be a ‘1’ logic value. In such cases, decoder may need to examine other bits of the DCI to distinguish the schemes 410 and 420 from each other.
  • the decoder may evaluate any other bits of the of DCI to distinguish between the second scheme 410 and the fourth scheme 420.
  • the decoder may evaluate the third bit (b 2 ) through the seventh bit (b 6 ) of the DCI to distinguish between the second scheme 410 and the fourth scheme 420.
  • These bits may be used to encode one or more HARQ identifiers. These bits may be encoded in a way that they unambiguous distinguish between the second scheme 410 and the fourth scheme 420. For the fourth scheme 420, these bits may be used to indicate whether one of seventy (70) different HARQ processes are used.
  • bits b 2 , b 3 , b 4 ⁇ 0, 0, 0 ⁇ in the fourth scheme 420 and bits b 5 , b 6 can either be ⁇ 0, 0 ⁇ , ⁇ 0, 1 ⁇ , or ⁇ 1, 0 ⁇ .
  • the encoder may shift the value of the HARQ index in bits b 2 , b 3 , b 4 , b 5 , b 6 of the second scheme 410 by some shift value. In the specific example, the encoder may use the shift value of three (3) .
  • Combinatorial HARQ index, for both the second scheme 410 and the fourth scheme 420 (or any scheme for that matter) may be determined using Equation 7 below. The is the combinatorial index mapping the HARQ processes scheduled, and is given by Equation 7.
  • FIG. 5 shows a diagram 500 of a device 505 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 505 may be an example of aspects of a UE 115 as described herein.
  • the device 505 may include a receiver 510, a communication manager 515, and a transmitter 520.
  • the device 505 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 510 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 downlink control information for scheduling one or more transport blocks, etc. ) . Information may be passed on to other components of the device 505.
  • the receiver 510 may be an example of aspects of the transceiver 815 described with reference to FIG. 8.
  • the receiver 510 may utilize a single antenna or a set of antennas.
  • the communication manager 515 may be configured to decode downlink control information based on a numerical quantity of transport blocks scheduled by the downlink control information.
  • the communication manager 515 may be an example of aspects of the communication manager 810 described herein.
  • the communication manager 515 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 communication manager 515, 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 communication manager 515 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 communication manager 515, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communication manager 515, 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 520 may transmit signals generated by other components of the device 505.
  • the transmitter 520 may be collocated with a receiver 510 in a transceiver module.
  • the transmitter 520 may be an example of aspects of the transceiver 815 described with reference to FIG. 8.
  • the transmitter 520 may utilize a single antenna or a set of antennas.
  • FIG. 6 shows a diagram 600 of a device 605 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 605 may be an example of aspects of a device 505, or a UE 115 as described herein.
  • the device 605 may include a receiver 610, a communication manager 615, and a transmitter 630.
  • the device 605 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 610 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 downlink control information for scheduling one or more transport blocks, etc. ) . Information may be passed on to other components of the device 605.
  • the receiver 610 may be an example of aspects of the transceiver 815 described with reference to FIG. 8.
  • the receiver 610 may utilize a single antenna or a set of antennas.
  • the communication manager 615 may be an example of aspects of the communication manager 515 as described herein.
  • the communication manager 615 may include a receiver 610, a transport block manager 620, and a decoding manager 625.
  • the communication manager 615 may be an example of aspects of the communication manager 810 described herein.
  • the receiver 610 may receive a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE and receive the one or more transport blocks from a base station based on the downlink control information.
  • the transport block manager 620 may identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks.
  • the decoding manager 625 may decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme.
  • the transmitter 630 may transmit signals generated by other components of the device 605.
  • the transmitter 630 may be collocated with a receiver 610 in a transceiver module.
  • the transmitter 630 may be an example of aspects of the transceiver 815 described with reference to FIG. 8.
  • the transmitter 630 may utilize a single antenna or a set of antennas.
  • FIG. 7 shows a diagram 700 of a communication manager 705 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the communication manager 705 may be an example of aspects of a communication manager 515, a communication manager 615, or a communication manager 810 described herein.
  • the communication manager 705 may include a receiver 710, a transport block manager 715, a decoding manager 720, a signaling manager 725, a coverage enhancement mode manager 730, a redundancy version manager 735, a frequency hopping manager 740, a MCS manager 745, a HARQ manager 750, and a joint decoding manager 755.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the receiver 710 may receive a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE. In some examples, the receiver 710 may receive the one or more transport blocks from a base station based on the downlink control information.
  • 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 downlink control information for scheduling one or more transport blocks, etc. ) . Information may be passed on to other components of the communication manager 705.
  • the receiver 710 may be an example of aspects of the transceiver 715 described with reference to FIG. 7.
  • the receiver 710 may utilize a single antenna or a set of antennas.
  • the transport block manager 715 may identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks. In some examples, the transport block manager 715 may determine the numerical quantity of the one or more transport blocks associated with the downlink control information block, where identifying the encoding scheme is based on determining the numerical quantity. In some examples, the transport block manager 715 may determine a set of transport blocks including one or more numerical quantities of transport blocks associated with the downlink control information block, where identifying the encoding scheme is based on determining the set of transport blocks.
  • the transport block manager 715 may identify a value of a field of the downlink control information block that indicates the numerical quantity of the one or more transport blocks scheduled by the downlink control information, where identifying the encoding scheme is based on identifying the value of the field.
  • the field is different lengths for different numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a prefix-free encoded value for a first portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a non-prefix-free encoded value for a second portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the transport block manager 715 may identify that the value of the field includes a non-prefix-free encoding value, and may identify a value of one or more bits outside of the field based on identifying that the value of the field includes the non-prefix-free encoding value, where identifying the encoding scheme is based on identifying the value of the one or more bits outside of the field. In some examples, the transport block manager 715 may identify that a first bit of the value of the field includes a first value, where identifying that the value of the field includes the non-prefix-free encoding value based on identifying that the first bit of the value of the field includes the first value. In some cases, the one or more bits are part of a field indicating a hybrid automatic repeat request configuration.
  • the decoding manager 720 may decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme.
  • the signaling manager 725 may identify a field of the downlink control information block that indicates the encoding scheme, where identifying the encoding scheme is based on the field. In some examples, the signaling manager 725 may determine the encoding scheme or the numerical quantity implicitly from the downlink control information block for indicating one or more configurations about the one or more transport blocks, where identifying the numerical quantity is based on determining the encoding scheme from the downlink control information block.
  • the coverage enhancement mode manager 730 may identify a coverage enhancement mode of the UE, where decoding the downlink control information block to obtain the downlink control information is based on the coverage enhancement mode of the UE.
  • the redundancy version manager 735 may identify a redundancy version for the one or more transport blocks indicated in the downlink control information based on the identified encoding scheme, where receiving the one or more transport blocks is based on identifying the redundancy version. In some examples, determining that the downlink control information does not include a field to indicate the redundancy version based on the encoding scheme, where identifying the redundancy version includes identifying a default redundancy version. In some cases, the redundancy version indicated in the downlink control information includes a common redundancy version for the one or more transport blocks based on the numerical quantity.
  • the frequency hopping manager 740 may identify a field of the downlink control information to indicate a frequency hopping configuration for the one or more transport blocks based on the encoding scheme, where receiving the one or more transport blocks is based on the frequency hopping configuration indicated by the downlink control information.
  • the frequency hopping manager 740 may determine that the downlink control information does not include a field to indicate a frequency hopping configuration for the one or more transport blocks based at least in part on the encoding scheme, and identify the frequency hopping configuration for the one or more transport blocks based at least in part on a radio resource configuration of the UE, where receiving the one or more transport blocks is based at least in part on identifying the redundancy version.
  • the MCS manager 745 may identify a second numerical quantity of bits of the downlink control information for indicating a modulation and coding scheme of the one or more transport blocks based on the encoding scheme associated with the downlink control information block. In some examples, the MCS manager 745 may identify the modulation and coding scheme of the one or more transport blocks based on the second numerical quantity of bits, where receiving the one or more transport blocks is based on identifying the modulation and coding scheme.
  • the HARQ manager 750 may identify one or more hybrid automatic repeat request processes associated with the one or more transport blocks based on a combinatorial number indicated by the downlink control information, the combinatorial number indicating a single combination of the one or more hybrid automatic repeat request processes with the encoding scheme.
  • the joint decoding manager 755 may decode, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a hybrid automatic repeat request configuration and a second parameter indicating a new data indicator, where decoding the downlink control information block is based on decoding the field.
  • the joint decoding manager 755 may decode, jointly accordingly to the encoding scheme, a field to identify a first parameter indicating a modulation and coding scheme configuration and a second parameter indicating a repetition number, where decoding the downlink control information block is based on decoding the field.
  • the joint decoding manager 755 may apply the at least one field of the downlink control information block that is jointly decoded to a combinatorial algorithm to determine a first configuration and a second configuration indicated by the at least one field.
  • the at least one field of the downlink control information block that is jointly decoded includes a combinatorial index mapping for at least two parameters associated with the one or more transport blocks.
  • jointly decoding the at least one field of the downlink control information block is independent of the numerical quantity of the one or more transport blocks.
  • FIG. 8 shows a diagram of a system 800 including a device 805 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 805 may be an example of or include the components of device 505, device 605, or a UE 115 as described herein.
  • the device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communication manager 810, a transceiver 815, an antenna 820, memory 825, and a processor 835. These components may be in electronic communication via one or more buses (e.g., bus 840) .
  • buses e.g., bus 840
  • the communication manager 810 may perform the features and functions described with reference to the communications managers of FIGs. 4, 5, and 6.
  • the transceiver 815 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 815 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 820. However, in some cases the device may have more than one antenna 820, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 825 may include RAM and ROM.
  • the memory 825 may store computer-readable, computer-executable code 830 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 825 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 code 830 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 830 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory.
  • the code 830 may not be directly executable by the processor 835 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the processor 835 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 835 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 835.
  • the processor 835 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 825) to cause the device 805 to perform various functions (e.g., functions or tasks supporting downlink control information for scheduling one or more transport blocks) .
  • FIG. 9 shows a diagram 900 of a device 905 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 905 may be an example of aspects of a base station 105 as described herein.
  • the device 905 may include a receiver 910, a communication manager 915, and a transmitter 920.
  • the device 905 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 910 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 downlink control information for scheduling one or more transport blocks, etc. ) . Information may be passed on to other components of the device 905.
  • the receiver 910 may be an example of aspects of the transceiver 1220 described with reference to FIG. 12.
  • the receiver 910 may utilize a single antenna or a set of antennas.
  • the communication manager 915 may be configured to encode downlink control information based on a numerical quantity of transport blocks scheduled by the downlink control information.
  • the communication manager 915 may be an example of aspects of the communication manager 1210 described herein.
  • the communication manager 915 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 communication manager 915, 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 communication manager 915 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 communication manager 915, or its sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure.
  • the communication manager 915, 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 920 may transmit signals generated by other components of the device 905.
  • the transmitter 920 may be collocated with a receiver 910 in a transceiver module.
  • the transmitter 920 may be an example of aspects of the transceiver 1220 described with reference to FIG. 12.
  • the transmitter 920 may utilize a single antenna or a set of antennas.
  • FIG. 10 shows a diagram 1000 of a device 1005 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 1005 may be an example of aspects of a device 905, or a base station 115 as described herein.
  • the device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020.
  • the device 1005 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 1010 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 downlink control information for scheduling one or more transport blocks, etc. ) . Information may be passed on to other components of the device 1005.
  • the receiver 1010 may be an example of aspects of the transceiver 1220 described with reference to FIG. 12.
  • the receiver 1010 may utilize a single antenna or a set of antennas.
  • the communication manager 1015 may be an example of aspects of the communication manager 915 as described herein.
  • the communication manager 1015 may include a transmitter 1020, a transport block manager 1025, an encoding scheme manager 1030, and an encoding manager 1035.
  • the communication manager 1015 may be an example of aspects of the communication manager 1210 described herein.
  • the transmitter 1020 may transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE and transmit the one or more transport blocks to the UE based on the downlink control information.
  • the transport block manager 1025 may determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information.
  • the encoding scheme manager 1030 may select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information.
  • the encoding manager 1035 may encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme.
  • the transmitter 1020 may transmit signals generated by other components of the device 1005.
  • the transmitter 1020 may be collocated with a receiver 1010 in a transceiver module.
  • the transmitter 1020 may be an example of aspects of the transceiver 1220 described with reference to FIG. 12.
  • the transmitter 1020 may utilize a single antenna or a set of antennas.
  • FIG. 11 shows a diagram 1100 of a communication manager 1105 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the communication manager 1105 may be an example of aspects of a communication manager 915, a communication manager 1015, or a communication manager 1210 described herein.
  • the communication manager 1105 may include a transmitter 1110, a transport block manager 1115, an encoding scheme manager 1120, an encoding manager 1125, a signaling manager 1130, a coverage enhancement manager 1135, a redundancy version manager 1140, a frequency hopping manager 1145, a MCS manager 1150, a HARQ manager 1155, and a joint encoding manager 1160.
  • Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
  • the transmitter 1110 may transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE. In some examples, the transmitter 1110 may transmit the one or more transport blocks to the UE based on the downlink control information.
  • the transmitter 1110 may transmit signals generated by other components of the communication manager 1105.
  • the transmitter 1110 may be collocated with a transmitter 1110 in a transceiver module.
  • the transmitter 1110 may be an example of aspects of the transceiver 1120 described with reference to FIG. 11.
  • the transmitter 1110 may utilize a single antenna or a set of antennas.
  • the transport block manager 1115 may determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information.
  • the field is different lengths for different numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a prefix-free encoded value for a first portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the field includes a non-prefix-free encoded value for a second portion of the numerical quantities of the one or more transport blocks scheduled by the downlink control information.
  • the transport block manager 1115 may identify that the value of the field includes a non-prefix-free encoding value and may shift a value of a parameter indicating a hybrid automatic repeat request configuration based on identifying that the value of the field includes a non-prefix-encoding value, where selecting the encoding scheme is based on shifting the value of the parameter.
  • the encoding scheme manager 1120 may select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information.
  • the encoding manager 1125 may encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme.
  • the signaling manager 1130 may identify a value of a field of the downlink control information for indicating the numerical quantity, where encoding the downlink control information into the downlink control information block is based on identifying the value. In some examples, the signaling manager 1130 may identify a value for one or more fields of the downlink control information for indicating one or more configurations about the one or more transport blocks based on the numerical quantity and one or more desired configurations of the one or more transport blocks, where encoding the downlink control information into the downlink control information block is based on identifying the value.
  • the coverage enhancement manager 1135 may identify a coverage enhancement mode associated with the UE, where selecting the encoding scheme for the downlink control information is based on the coverage enhancement mode associated with the UE.
  • the redundancy version manager 1140 may identify a redundancy version for the one or more transport blocks to indicate in the downlink control information based on the numerical quantity of the one or more transport blocks, where encoding the downlink control information is based on identifying the redundancy version. In some examples, the redundancy version manager 1140 may omit an indicator of a redundancy version from the downlink control information based on the numerical quantity, where encoding the downlink control information is based on omitting the indicator of the redundancy version from the downlink control information. In some cases, the redundancy version indicated in the downlink control information includes a common redundancy version for the one or more transport blocks based on the numerical quantity.
  • the frequency hopping manager 1145 may identify a field of the downlink control information to indicate a frequency hopping configuration for the one or more transport blocks based on the numerical quantity of the one or more transport blocks, where encoding the downlink control information is based on the frequency hopping configuration.
  • the frequency hopping manager 1145 may omit an indicator of a frequency hopping configuration from the downlink control information based at least in part on the numerical quantity, where encoding the downlink control information is based at least in part on omitting the indicator of the frequency hopping configuration from the downlink control information.
  • the MCS manager 1150 may identify a second numerical quantity of bits of the downlink control information for indicating a modulation and coding scheme of the one or more transport blocks based on the numerical quantity of the one or more transport blocks associated with the downlink control information, where encoding the downlink control information is based on identifying the second numerical quantity of bits of the downlink control information for indicating the modulation and coding scheme.
  • the MCS manager 1150 may identify a range of possible modulation and scheme configurations associated with the one or more transport blocks, where identifying the second numerical quantity of bits is based on identifying the range of possible modulation and coding scheme configurations.
  • the HARQ manager 1155 may assign a unique combinatorial number to each possible combination of hybrid automatic repeat request processes with the numerical quantity of the one or more transport blocks associated with the downlink control information, where the downlink control information includes the unique combinatorial number.
  • the joint encoding manager 1160 may encode, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a hybrid automatic repeat request configuration and a second parameter indicating a new data indicator, where encoding the downlink control information block is based on encoding the field.
  • the joint encoding manager 1160 may encode, jointly according to the encoding scheme, a field of the downlink control information block to identify a first parameter indicating a modulation and coding scheme configuration and a second parameter indicating a repetition number, where encoding the downlink control information block is based on encoding the field.
  • determining a combinatorial index mapping for the at least two parameters of the one or more transport blocks, where the at least one field of the downlink control information block that is jointly encoded includes the combinatorial index mapping.
  • the joint encoding manager 1160 may apply a first parameter and a second parameter to a combinatorial algorithm to determine a combinatorial index mapping for the at least one field of the downlink control information block that is jointly encoded.
  • jointly decoding the at least one field of the downlink control information block is independent of the numerical quantity of the one or more transport blocks.
  • FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the device 1205 may be an example of or include the components of device 905, device 1005, or a base station 105 as described herein.
  • the device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communication manager 1210, a network communications manager 1215, a transceiver 1220, an antenna 1225, memory 1230, a processor 1240, and an inter-station communications manager 1245. These components may be in electronic communication via one or more buses (e.g., bus 1250) .
  • buses e.g., bus 1250
  • the communication manager 1210 may perform the features and functions described with reference to the communications managers of FIGs. 8, 9, and 10.
  • the network communications manager 1215 may manage communications with the core network (e.g., via one or more wired backhaul links) .
  • the network communications manager 1215 may manage the transfer of data communications for client devices, such as one or more UEs 115.
  • the transceiver 1220 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above.
  • the transceiver 1220 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 1220 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 1225. However, in some cases the device may have more than one antenna 1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the memory 1230 may include RAM and ROM.
  • the memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed, cause the processor to perform various functions described herein.
  • the memory 1230 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 code 1235 may include instructions to implement aspects of the present disclosure, including instructions to support wireless communications.
  • the code 1235 may be stored in a non-transitory computer-readable medium such as system memory or other type of memory. In some cases, the code 1235 may not be directly executable by the processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the processor 1240 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 1240 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1240.
  • the processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting downlink control information for scheduling one or more transport blocks) .
  • the inter-station communications manager 1245 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 1245 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 1245 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations 105.
  • FIG. 13 shows a flowchart illustrating a method 1300 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1300 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1300 may be performed by a communication manager as described with reference to FIGs. 5 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions.
  • a UE may perform aspects of the described functions using special-purpose hardware.
  • the UE may receive a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE.
  • the operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed by a Receiver as described with reference to FIGs. 5 through 8.
  • the UE may identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks.
  • the operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed by a transport block manager as described with reference to FIGs. 5 through 8.
  • the UE may decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme.
  • the operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed by a decoding manager as described with reference to FIGs. 5 through 8.
  • the UE may receive the one or more transport blocks from a base station based on the downlink control information.
  • the operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operations of 1320 may be performed by a Receiver as described with reference to FIGs. 5 through 8.
  • FIG. 14 shows a flowchart illustrating a method 1400 that supports downlink control information for scheduling one or more transport blocks in accordance with aspects of the present disclosure.
  • the operations of method 1400 may be implemented by a UE 115 or its components as described herein.
  • the operations of method 1400 may be performed by a communication manager as described with reference to FIGs. 5 through 8.
  • a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions.
  • a UE may perform aspects of the described functions using special-purpose hardware.
  • the UE may receive a downlink control information block including downlink control information for one or more transport blocks scheduled for the UE.
  • the operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed by a Receiver as described with reference to FIGs. 5 through 8.
  • the UE may determine the numerical quantity of the one or more transport blocks associated with the downlink control information block, where identifying the encoding scheme is based on determining the numerical quantity.
  • the operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed by a transport block manager as described with reference to FIGs. 5 through 8.
  • the UE may identify an encoding scheme used to encode the downlink control information block based on a bitstream of the downlink control information block, where the encoding scheme is associated with a numerical quantity of the one or more transport blocks.
  • the operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed by a transport block manager as described with reference to FIGs. 5 through 8.
  • the UE may decode the downlink control information block to obtain the downlink control information for the one or more transport blocks based on the identified encoding scheme.
  • the operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed by a decoding manager as described with reference to FIGs. 5 through 8.
  • the UE may receive the one or more transport blocks from a base station based on the downlink control information.
  • the operations of 1425 may be performed according to the methods described herein. In some examples, aspects of the operations of 1425 may be performed by a Receiver as described with reference to FIGs. 5 through 8.
  • FIG. 15 shows a flowchart illustrating a method 1500 that supports downlink control information for scheduling one or more 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 communication manager as described with reference to FIGs. 9 through 12.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, a base station may perform aspects of the described functions using special-purpose hardware.
  • the base station may determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information.
  • 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 manager as described with reference to FIGs. 9 through 12.
  • the base station may select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information.
  • 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 an encoding scheme manager as described with reference to FIGs. 9 through 12.
  • the base station may encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme.
  • 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 encoding manager as described with reference to FIGs. 9 through 12.
  • the base station may transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE.
  • 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 Transmitter as described with reference to FIGs. 9 through 12.
  • the base station may transmit the one or more transport blocks to the UE based on the downlink control information.
  • the operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operations of 1525 may be performed by a Transmitter as described with reference to FIGs. 9 through 12.
  • FIG. 16 shows a flowchart illustrating a method 1600 that supports downlink control information for scheduling one or more 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 communication manager as described with reference to FIGs. 9 through 12.
  • a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally or alternatively, a base station may perform aspects of the described functions using special-purpose hardware.
  • the base station may determine a numerical quantity of one or more transport blocks for a UE scheduled by downlink control information.
  • 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 manager as described with reference to FIGs. 9 through 12.
  • the base station may identify a coverage enhancement mode associated with the UE, where selecting the encoding scheme for the downlink control information is based on the coverage enhancement mode associated with the UE.
  • 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 coverage enhancement manager as described with reference to FIGs. 9 through 12.
  • the base station may select an encoding scheme for the downlink control information based on the numerical quantity of the one or more transport blocks associated with the downlink control information.
  • 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 an encoding scheme manager as described with reference to FIGs. 9 through 12.
  • the base station may encode the downlink control information into a downlink control information block for the one or more transport blocks based on the encoding scheme.
  • 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 encoding manager as described with reference to FIGs. 9 through 12.
  • the base station may transmit, to the UE, the downlink control information block for the one or more transport blocks to the UE.
  • 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 Transmitter as described with reference to FIGs. 9 through 12.
  • the base station may transmit the one or more transport blocks to the UE based on the downlink control information.
  • 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 Transmitter as described with reference to FIGs. 9 through 12.
  • LTE, LTE-A, LTE-A Pro, or NR 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 networks.
  • the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
  • UMB Ultra Mobile Broadband
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Institute of Electrical and Electronics Engineers
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • 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 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 and spirit of the disclosure and appended claims. For example, due to the nature of software, functions described above 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.
  • the term “and/or, ” when used in a list of two or more items means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed.
  • the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
  • “or” as used in a list of items indicates a disjunctive list such that, for example, a list of “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • 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 may be accessed by a general-purpose or special purpose computer.
  • non-transitory computer-readable media may include random-access memory (RAM) , read-only memory (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 may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
  • RAM random-access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable ROM
  • flash memory compact disk (CD) ROM or other optical disk storage
  • CD compact disk
  • magnetic disk storage or other magnetic storage devices or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer,
  • 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)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés, des systèmes et des dispositifs pour des communications sans fil. L'invention concerne des techniques pour coder des informations de contrôle de liaison descendante (DCI) sur la base du nombre de blocs de transport qui sont ordonnancés par les DCI. Le nombre de blocs de transport pris en charge par les DCI peut être indiqué explicitement à l'aide d'un champ inclus dans les DCI. Le nombre de blocs de transport peut être implicitement signalé dans un flux binaire du bloc DCI. Le type de schéma de codage peut être basé sur le mode d'amélioration de couverture (CE) associé à un équipement utilisateur.
EP19948031.0A 2019-10-04 2019-11-18 Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport Pending EP4039028A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/109824 WO2021062876A1 (fr) 2019-10-04 2019-10-04 Informations de commande de liaison descendante pour planifier un ou plusieurs blocs de transport
PCT/CN2019/119110 WO2021062925A1 (fr) 2019-10-04 2019-11-18 Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport

Publications (2)

Publication Number Publication Date
EP4039028A1 true EP4039028A1 (fr) 2022-08-10
EP4039028A4 EP4039028A4 (fr) 2023-10-18

Family

ID=75336678

Family Applications (1)

Application Number Title Priority Date Filing Date
EP19948031.0A Pending EP4039028A4 (fr) 2019-10-04 2019-11-18 Informations de contrôle de liaison descendante pour planifier un ou plusieurs blocs de transport

Country Status (4)

Country Link
US (1) US12127216B2 (fr)
EP (1) EP4039028A4 (fr)
CN (1) CN114451049A (fr)
WO (2) WO2021062876A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111092692A (zh) * 2019-11-08 2020-05-01 中兴通讯股份有限公司 一种控制信息指示方法、通信节点及计算机可读存储介质
US11937260B2 (en) * 2020-10-14 2024-03-19 Lg Electronics Inc. Method and apparatus for transmitting/receiving wireless signal in wireless communication system
WO2023216047A1 (fr) * 2022-05-09 2023-11-16 Qualcomm Incorporated Sélection de ressource de liaison latérale sans licence (sl-u) pour procédure d'écoute avant de transmettre (lbt)

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8724648B2 (en) 2009-09-30 2014-05-13 Nokia Corporation Enhanced control signaling for backhaul link
US11057921B2 (en) * 2014-10-01 2021-07-06 Samsung Electronics Co., Ltd. System and method for improving spectral efficiency and coverage for user equipments
US9979581B2 (en) * 2016-04-01 2018-05-22 Mediatek Inc. Control channel design for eLAA
WO2018071104A1 (fr) * 2016-10-10 2018-04-19 Intel IP Corporation Équipement utilisateur (ue), nœud b évolué (enb) et procédés de demande de répétition automatique hybride (harq) dynamique
US10673593B2 (en) * 2016-11-03 2020-06-02 Huawei Technologies Co., Ltd. HARQ signaling for grant-free uplink transmissions
US10652866B2 (en) * 2017-03-20 2020-05-12 Huawei Technologies Co., Ltd. Systems and methods for supporting asynchronous uplink HARQ and multiple simultaneous transmissions
WO2018175896A1 (fr) * 2017-03-24 2018-09-27 Intel IP Corporation Prise en charge d'une modulation maq 64 pour une transmission sur pdsch efemtc
CN109428668B (zh) 2017-07-20 2021-06-22 华为技术有限公司 一种数据传输的方法及设备
US11025456B2 (en) * 2018-01-12 2021-06-01 Apple Inc. Time domain resource allocation for mobile communication
US11095482B2 (en) * 2018-04-30 2021-08-17 Apple Inc. Channel state information reference signal (CSI-RS) and sounding reference signal (SRS) triggering
WO2020118632A1 (fr) 2018-12-13 2020-06-18 Qualcomm Incorporated Conception d'informations de commande de liaison descendante pour la planification de multiples blocs de transport
CN110383748B (zh) 2019-05-09 2022-05-13 北京小米移动软件有限公司 下行控制信息发送方法、装置及可读存储介质

Also Published As

Publication number Publication date
EP4039028A4 (fr) 2023-10-18
CN114451049A (zh) 2022-05-06
US12127216B2 (en) 2024-10-22
WO2021062876A1 (fr) 2021-04-08
WO2021062925A1 (fr) 2021-04-08
US20230156718A1 (en) 2023-05-18

Similar Documents

Publication Publication Date Title
US11991701B2 (en) Time domain resource allocation for downlink data repetitions
KR20220163383A (ko) 5g(fifth generation) nr(new radio) 안테나 스위칭 동시성의 관리
US11646826B2 (en) Message repetition configurations for random access procedures
US11690104B2 (en) Message repetition configurations for random access procedures
US11564248B2 (en) Techniques for activation and deactivation of resources configured across multiple component carriers
US12127216B2 (en) Downlink control information for scheduling one or more transport blocks
WO2021183264A1 (fr) Modulation d'indice en duplex intégral
US11909691B2 (en) On-demand negative acknowledgment resource request
CN117716648A (zh) 用于复用多比特反馈和单比特反馈的技术
US12075427B2 (en) Techniques for releasing multiple sets of semi-persistent scheduling and configured grant resources
US12058682B2 (en) Handling collisions between a feedback message and uplink control information
CN115413404B (zh) 两阶段反馈规程
US11368263B2 (en) Group hopping enhancement for base sequences
WO2022026217A1 (fr) Techniques permettant d'activer et de libérer des ressources à travers de multiples porteuses composantes
CN116998123A (zh) 侧行链路上的反馈发送与接收之间的优先化
US11889502B2 (en) Two-stage feedback procedures
US20220240245A1 (en) Generating a feedback codebook
US20230090447A1 (en) Resources for uplink control information multiplexing in an absence of demodulation reference signals
US20230122908A1 (en) Interleaving techniques for wireless communications systems
KR20240136337A (ko) 업링크 제어 정보 비트들의 압축된 시퀀스
CN118355624A (zh) 用于使用基于cdm群组的dmrs端口映射的多码字通信的技术

Legal Events

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

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

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220224

AK Designated contracting states

Kind code of ref document: A1

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

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20230915

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 72/12 20090101AFI20230911BHEP