Signaling of alternative modulation and coding schemes using scaling factors

Abstract

Wireless devices may employ techniques for indicating alternative modulation and coding schemes (MCSs) (e.g., MCS values ​​or MCS indices unrelated to the default list or default MCS table). That is, communications (e.g., transmission of a Physical Downlink Control Channel (PDCCH) carrying downlink control information (DCI), transmission of a Physical Downlink Shared Channel (PDSCH) carrying uplink clearance, etc.) may include information indicating alternative MCSs for subsequent communications (e.g., in MCS fields and reserved fields). For example, a DCI scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a Random Access Response (RAR) message, etc., may indicate alternative MCSs for subsequent messages during the random access process (e.g., for RAR, RRC connection requests, etc.). Alternative MCSs can be conveyed by information such as an MCS scaling factor, the ID of the alternative MCS table, an MCS index associated with the alternative MCS table, or some combination thereof.

Description

[0001] This application is a divisional application of the invention patent application filed on March 7, 2019, with application number 201980023971.9 and title "Signaling using an alternative modulation coding scheme with scaling factor".

[0002] Cross-references

[0003] This patent application claims the benefit of U.S. Patent Application No. 16 / 119,904, entitled “SIGNALING OF ALTERNATIVE MODULATION CODING SCHEMES”, filed by BAI et al. on August 31, 2018, and U.S. Provisional Patent Application No. 62 / 653,497, entitled “SIGNALING OF ALTERNATIVE MODULATION CODINGSCHEMES”, filed by BAI et al. on April 5, 2018, each of which is assigned to the assignee and is expressly incorporated herein by reference in its entirety. Background Technology

[0004] The following generally pertains to wireless communication, and more specifically to signaling for alternative modulation and coding schemes (MCS).

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), or LTE-A Pro systems, and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended OFDM (DFT-S-OFDM). A wireless multiple access communication system may include multiple base stations or network access nodes, each supporting communication from multiple communication devices simultaneously, which may be referred to as User Equipment (UE). Base stations can communicate with mobile devices (e.g., UEs) via downlink and uplink. Downlink (or forward link) can refer to the communication link from the base station to the UE, while uplink (or reverse link) can refer to the communication link from the UE to the base station.

[0006] During communication, wireless devices (e.g., base stations, UEs, etc.) may employ different modulation and coding schemes (MCS) (e.g., different implementations of modulation schemes, coding rates, transport block sizes (TBS), spatial streams, etc.) to address different system requirements. For example, a higher coding rate may be associated with increased data throughput but may be more sensitive to interference and multipath problems, while a lower coding rate may provide more robust communication but may be associated with a lower data rate. In some examples, base stations and UEs may access an MCS table to determine the MCS used for uplink or downlink transmission. However, wireless communication systems may also support additional MCSs, and the standard or default MCS table may not include data entries (e.g., MCS values) that take into account these alternative MCSs that the communication system can support. Therefore, improved techniques may be desired for determining and indicating these alternative MCSs (e.g., MCS values ​​not included in the default table). Summary of the Invention

[0007] The described technology relates to methods, systems, devices, and apparatuses for improving signaling that supports alternative modulation and coding schemes (MCS). In general, the described technology provides wireless devices with indications for and determination of alternative MCS (e.g., MCS values ​​or MCS indices unrelated to a default list or default MCS table). That is, communications (e.g., transmission of a Physical Downlink Control Channel (PDCCH) carrying downlink control information (DCI), transmission of a Physical Downlink Shared Channel (PDSCH) carrying uplink clearance, etc.) may include information indicating alternative MCSs for subsequent communications (e.g., in MCS fields and reserved fields). For example, a DCI message scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a Random Access Response (RAR) message, etc., can indicate alternative MCSs for subsequent messages during the random access process (e.g., for RAR, RRC connection requests, etc.).

[0008] An alternative MCS can be conveyed by including the MCS field and reserved fields in the transmission (e.g., in RA-RNTI scrambled DCI, in RAR messages, etc.). For example, a reserved field can indicate a scaling factor that can be used with the MCS indicated by the MCS field to indicate or determine an alternative MCS (e.g., by multiplying one or more aspects of the indicated MCS, such as the bitrate, by the indicated scaling factor). In other examples, a reserved field can indicate the use of an alternative (e.g., a non-default) MCS table. A reserved field can include an indication of an alternative MCS table that can be used with an MCS index indicated by the MCS field (e.g., an MCS index indicated by the MCS field can be used with the indicated alternative MCS table to determine an alternative MCS). Alternatively, the reserved field itself can indicate an MCS index associated with the alternative MCS field (e.g., in some cases, the MCS field can be unused or set to all zeros to indicate that the reserved field indicates an MCS index associated with the alternative MCS table).

[0009] A wireless communication method is described. The method may include: identifying a default set of MCS values ​​and receiving at the UE a DCI message including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The method may further include: receiving PDSCH transmissions from a base station based on the default set of MCS values ​​and the scaling factor.

[0010] An apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be processor-executable to cause the apparatus to recognize a default set of MCS values ​​and receive a DCI message at the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The instructions may also be processor-executable to cause the apparatus to receive PDSCH transmissions from a base station based on the default set of MCS values ​​and the scaling factor.

[0011] Another apparatus for wireless communication is described. The apparatus may include: components for identifying a default set of MCS values ​​and components for receiving a DCI message at the UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The apparatus may also include components for receiving PDSCH transmissions from a base station based on the default set of MCS values ​​and the scaling factor.

[0012] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include processor-executable instructions to identify a default set of MCS values ​​and receive a DCI message at the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The code may include additional instructions operable to cause the processor to receive PDSCH transmissions from the base station based on the default set of MCS values ​​and the scaling factor.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, PDSCH transmission includes RAR messages. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a random access preamble to a base station, wherein the RAR message may be in response to the random access preamble.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RAR message includes a second message (Msg2) during the random access procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the DCI message may be scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a System Information Radio Network Temporary Identifier (SI-RNTI), a Paging Radio Network Temporary Identifier (P-RNTI), or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining the MCS value for PDSCH transmission based at least in part on multiplying the MCS value in a default set of MCS values ​​by a scaling factor.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, multiplying an MCS value in a default set of MCS values ​​with a scaling factor may further include an operation, feature, component, or instruction for identifying a code rate associated with an MCS value in the default set of MCS values ​​and multiplying the identified code rate with a scaling factor, wherein the code rate associated with the determined MCS value for PDSCH transmission may be based on this multiplication.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of an MCS value from a default set of MCS values, wherein multiplication may be based on an indication of an MCS value from the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the default set of MCS values ​​correspond to the lowest MCS value in the default set of MCS values.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the scaling factor may be an indication of whether the MCS value used for PDSCH transmission can be included in the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of whether the MCS value used for PDSCH transmission can be included in the default set of MCS values ​​includes at least one bit in the reserved field of the DCI message.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication that the MCS value for PDSCH transmission is included in a second set of MCS values. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of an MCS value in a second set of MCS values, wherein the MCS value for PDSCH transmission can be determined based on the received indication of the MCS value in the second set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the second set of MCS values ​​indicate a code rate, modulation scheme, or a combination thereof.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of the MCS values ​​in the second MCS value set may be an indication that the MCS values ​​used for PDSCH transmission can be included in the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of whether the MCS values ​​used for PDSCH transmission can be included in the default MCS value set includes an indication that the MCS values ​​used for PDSCH transmission can be included in the second MCS value set.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an MCS index field and identifying an index associated with a second MCS value set based on an indication of whether the MCS index field and the MCS value used for PDSCH transmission can be included in a default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS value in the second MCS value set includes at least one bit in a reserved field of the DCI message.

[0022] A method for wireless communication is described. The method may include: identifying a default set of MCS values ​​and receiving a downlink message at a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The method may further include transmitting uplink transmissions to a base station based on the default set of MCS values ​​and the scaling factor.

[0023] An apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be processor-executable to cause the apparatus to recognize a default set of MCS values ​​and receive a downlink message at a UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The instructions may also be processor-executable to cause the apparatus to transmit uplink transmissions to a base station based on the default set of MCS values ​​and the scaling factor.

[0024] Another apparatus for wireless communication is described. The apparatus may include: components for identifying a default set of MCS values ​​and components for receiving a downlink message at a UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The apparatus may further include components for transmitting uplink transmissions to a base station based on the default set of MCS values ​​and the scaling factor.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include processor-executable instructions to identify a default set of MCS values ​​and receive a downlink message at the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The code may include additional processor-executable instructions to transmit uplink transmissions to a base station based on the default set of MCS values ​​and the scaling factor.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the downlink message is a RAR message, and the uplink transmission is an RRC connection request message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an RRC connection request in response to a RAR message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RAR message may be Msg2 in a random access procedure, and the RRC connection request message includes a third message (Msg3) in the random access procedure.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining an MCS value for an RRC connection request message based at least in part on multiplying an MCS value from a default set of MCS values ​​by a scaling factor. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, multiplying an MCS value from a default set of MCS values ​​by a scaling factor may also include operations, features, components, or instructions for identifying a code rate associated with an MCS value from the default set of MCS values ​​and multiplying the identified code rate by a scaling factor, wherein the code rate associated with the determined MCS value for the RRC connection request message may be based on this multiplication.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of an MCS value in a default set of MCS values, wherein multiplication may be based on an indication of an MCS value in the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the default set of MCS values ​​correspond to the lowest MCS value in the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the scaling factor may be an indication of whether the MCS value used for an RRC connection request message can be included in the default set of MCS values.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of whether the MCS value for an RRC connection request message can be included in a default set of MCS values ​​includes at least one bit in a reserved field of the RAR message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication that the MCS value for an RRC connection request message can be included in a second set of MCS values.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication of an MCS value in a second set of MCS values, wherein the MCS value for an RRC connection request message may be determined based on the indication of the received MCS values ​​in the second set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the second set of MCS values ​​indicate a code rate, modulation scheme, or a combination thereof.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of the MCS values ​​in the second MCS value set may be an indication of whether the MCS value for the RRC connection request message can be included in the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication of whether the MCS value for the RRC connection request message can be included in the default MCS value set may be an indication of whether the MCS value for the RRC connection request message can be included in the default MCS value set.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for identifying an index associated with a second set of MCS values ​​based on an indication that the MCS value for the RRC connection request message may be included in a second set of MCS values. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an MCS index field and, based on that MCS index field and an indication that the MCS value for the RRC connection request message may be included in a second set of MCS values, identifying an index associated with a second set of MCS values.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS value for an RRC connection request message may be included in a second set of MCS values, indicating that at least one bit of the reserved field of the RAR message is included.

[0034] A wireless communication method is described. The method may include: identifying a default set of MCS values, sending a DCI message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values, and sending PDSCH transmission to the UE based on the default set of MCS values ​​and the scaling factor.

[0035] An apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions, executable by the processor, enable the apparatus to recognize a default set of MCS values, send a DCI message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values, and send PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor.

[0036] Another apparatus for wireless communication is described. The apparatus may include: components for identifying a default set of MCS values; components for sending a DCI message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values; and components for sending PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor.

[0037] A non-transitory computer-readable medium is described, storing code for wireless communication. The code may include processor-executable instructions to identify a default set of MCS values, send a DCI message to the UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value for PDSCH transmission is included in the default set of MCS values, and instructions for sending PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor.

[0038] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, PDSCH transmission includes RAR messages. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a random access preamble from a UE, wherein the RAR message may be sent in response to the random access preamble. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RAR message may be Msg2 during a random access procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, DCI messages may be scrambled using RA-RNTI, SI-RNTI, P-RNTI, or TC-RNTI.

[0039] The methods, apparatuses, and non-transitory computer-readable media described herein provide examples of scaling factors that can be based on the MCS value used for PDSCH transmission and the MCS value in a default set of MCS values.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the scaling factor may be based on a code rate associated with the MCS value used for PDSCH transmission and a code rate associated with the MCS values ​​in a default set of MCS values. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting indications of MCS values ​​in the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the default set of MCS values ​​correspond to the lowest MCS value in the default set of MCS values.

[0041] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the scaling factor may be an indication of whether the MCS value used for PDSCH transmission can be included in a default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of whether the MCS value used for PDSCH transmission can be included in the default set of MCS values ​​includes at least one bit in the reserved field of the DCI message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for indicating whether to send MCS values ​​in a second set of MCS values, wherein the MCS values ​​in the second set of MCS values ​​may be based on the MCS values ​​used for PDSCH transmission.

[0042] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the second MCS value set indicate the code rate, modulation scheme, or a combination thereof. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS values ​​in the second MCS value set includes the MCS index and an indication of whether the MCS values ​​used for PDSCH transmission can be included in the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS values ​​in the second MCS value set can be an indication that the MCS values ​​used for PDSCH transmission can be included in the second MCS value set.

[0043] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication that the MCS value for PDSCH transmission can be included in a second MCS value set may indicate whether the MCS value for PDSCH transmission can be included in a default MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication that the MCS value for PDSCH transmission can be included in a second MCS value set also indicates an index associated with the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS value in the second MCS value set includes at least one bit in the reserved field of the DCI message.

[0044] A method for wireless communication is described. The method may include: identifying a default set of MCS values; sending a downlink message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values; and receiving uplink transmissions from the UE based on the default set of MCS values ​​and the scaling factor.

[0045] An apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions, executable by the processor, enable the apparatus to recognize a default set of MCS values, send a downlink message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values, and receive uplink transmissions from the UE based on the default set of MCS values ​​and the scaling factor.

[0046] Another apparatus for wireless communication is described. The apparatus may include: components for identifying a default set of MCS values; components for sending a downlink message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether an MCS value for uplink transmission is included in the default set of MCS values; and components for receiving uplink transmissions from the UE based on the default set of MCS values ​​and the scaling factor.

[0047] A non-transitory computer-readable medium is described, storing code for wireless communication. The code may include processor-executable instructions to identify a default set of MCS values, send a downlink message to a UE including an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values, and receive uplink transmissions from the UE based on the default set of MCS values ​​and the scaling factor.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, downlink messages include RAR messages, and uplink transmissions include RRC connection request messages. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RRC connection request message may be in response to the RAR message. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RAR message may be Msg2 in a random access procedure; and the RRC connection request message may be Msg3 in a random access procedure. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the scaling factor may be based on the MCS value used for the RRC connection request message and MCS values ​​from a default set of MCS values.

[0049] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the scaling factor may be based on a code rate associated with the MCS value used for the RRC connection request message and a code rate associated with MCS values ​​in a default set of MCS values. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication of MCS values ​​in the default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the default set of MCS values ​​correspond to the lowest MCS value in the default set of MCS values.

[0050] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the scaling factor may be an indication of whether the MCS value for an RRC connection request message can be included in a default set of MCS values. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of whether the MCS value for an RRC connection request message can be included in a default set of MCS values ​​includes at least one bit in a reserved field of the DCI message. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication that the MCS value for an RRC connection request message can be included in a second set of MCS values.

[0051] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting indications of MCS values ​​in a second set of MCS values, wherein the MCS values ​​in the second set of MCS values ​​may be based on the MCS values ​​used for RRC connection request messages. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the MCS values ​​in the second set of MCS values ​​indicate a code rate, modulation scheme, or a combination thereof.

[0052] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS values ​​in the second MCS value set may be an indication that the MCS value for the RRC connection request message can be included in the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the MCS values ​​in the second MCS value set includes an MCS index and an indication that the MCS value for the RRC connection request message can be included in the second MCS value set.

[0053] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication that the MCS value for an RRC connection request message can be included in a second MCS value set may indicate whether the MCS value for an RRC connection request message can be included in a default MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication that the MCS value for an RRC connection request message can be included in a second MCS value set also indicates an index associated with the second MCS value set. In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, an indication that the MCS value for an RRC connection request message can be included in a second MCS value set includes at least one bit in the reserved fields of the RAR message.

[0054] This document describes a method for wireless communication, comprising: identifying a default set of modulation and coding scheme (MCS) parameters; receiving at a user equipment (UE) a downlink control information (DCI) message scrambled by a radio network temporary identifier (RNTI), wherein the RNTI-scrambled DCI message indicates non-default MCS parameters for physical downlink shared channel (PDSCH) transmission; and receiving the PDSCH transmission from a base station based at least in part on the non-default MCS parameters.

[0055] This document describes a method for wireless communication, comprising: identifying a default set of modulation and coding scheme (MCS) parameters; receiving at a user equipment (UE) a downlink control information (DCI) message scrambled by a radio network temporary identifier (RNTI), wherein the RNTI-scrambled DCI message indicates non-default MCS parameters for physical downlink shared channel (PDSCH) transmission; and transmitting the PDSCH transmission to the UE at least in part based on the non-default MCS parameters.

[0056] This document describes an apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to cause the apparatus to: identify a default set of modulation and coding scheme (MCS) parameters; receive at a user equipment (UE) a downlink control information (DCI) message scrambled by a radio network temporary identifier (RNTI), wherein the RNTI-scrambled DCI message indicates non-default MCS parameters for physical downlink shared channel (PDSCH) transmission; and receive PDSCH transmissions from a base station based at least in part on the non-default MCS parameters.

[0057] This document describes an apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors being configured to cause the apparatus to: identify a default set of modulation and coding scheme (MCS) parameters; transmit at a user equipment (UE) a downlink control information (DCI) message scrambled by a radio network temporary identifier (RNTI), wherein the RNTI-scrambled DCI message indicates non-default MCS parameters for physical downlink shared channel (PDSCH) transmission; and transmit the PDSCH transmission to the UE at least in part based on the non-default MCS parameters. Attached Figure Description

[0058] Figure 1 An example of a wireless communication system that supports signaling for alternative MCSs according to various aspects of this disclosure is illustrated.

[0059] Figure 2 An example of a wireless communication system that supports signaling for alternative MCSs according to various aspects of this disclosure is illustrated.

[0060] Figure 3 An example of the signaling processing flow supporting alternative modulation and coding schemes (MCS) according to various aspects of this disclosure is illustrated.

[0061] Figure 4 An example of the signaling processing flow for an alternative MCS according to various aspects of this disclosure is illustrated.

[0062] Figure 5 and Figure 6 A block diagram of a device supporting signaling for alternative MCSs according to various aspects of this disclosure is shown.

[0063] Figure 7 A block diagram of a device supporting signaling for alternative MCSs according to various aspects of this disclosure is shown.

[0064] Figure 8 A diagram of a system including signaling devices supporting alternative MCSs according to various aspects of this disclosure is shown.

[0065] Figure 9 and Figure 10 A block diagram of a device supporting signaling for alternative MCSs according to various aspects of this disclosure is shown.

[0066] Figure 11 A block diagram of a device supporting signaling for alternative MCSs according to various aspects of this disclosure is shown.

[0067] Figure 12 A diagram of a system including signaling devices supporting alternative MCSs according to various aspects of this disclosure is shown.

[0068] Figures 13 to 19 A flowchart illustrating a signaling method for supporting alternative MCSs according to various aspects of this disclosure is shown. Detailed Implementation

[0069] During communication, wireless devices (e.g., base stations, user equipment (UEs), etc.) may employ different modulation and coding schemes (MCS) (e.g., different implementations of modulation schemes, coding rates, transport block sizes (TBS), spatial streams, etc.) to address different system requirements. For example, a higher coding rate may be associated with increased data throughput, but may be more sensitive to interference and multipath problems (while a lower coding rate may provide more robust communication, but may be associated with a lower data rate).

[0070] Additionally, wireless devices (e.g., base stations, UEs, etc.) can use beamed or beamformed signals to transmit and / or receive wireless communications. Therefore, wireless devices can use directional transmit beams to transmit signals and can use certain antenna configurations or receive beams to receive signals. For example, a base station can utilize beamformed transmission to mitigate path loss associated with high-frequency communications. A base station can use downlink transmit beams that can be associated with a coverage area (e.g., a coverage area that may be referred to as a cell) to transmit messages.

[0071] In some cases (e.g., during initial cell acquisition), the beam used for transmission may not be properly refined (e.g., due to the lack of an established Radio Resource Control (RRC) connection, the lack of a beam refinement process, etc.). For example, a base station may transmit a Synchronization Signal Block (SSB) carrying a System Information Block (SSB) (e.g., including information such as cell ID, common and shared channel information, RRC uplink power control, cyclic prefix length, etc.) for UE cell access. The UE can monitor the SSB and initiate a random access procedure (e.g., a Random Access Channel (RACH) procedure, a Physical RACH (PRACH) procedure, etc.) to establish an RRC connection with the base station. Due to the lack of an established RRC connection (e.g., the lack of a beam refinement process, prior to the communication of channel and transmission parameters, etc.), messages exchanged during the random access procedure may suffer from low signal-to-noise ratio (SNR), high carrier frequency offset, etc. For example, beamforming and frequency synchronization associated with a Random Access Response (RAR) (e.g., Random Access Message 2 (Msg2)) or Radio Resource Control (RRC) connection request (e.g., Random Access Message 3 (Msg3)) may not be refined, and the RAR may be associated with low SNR and / or high carrier frequency offset because timing and carrier frequency information may not have been well synchronized. Similar problems may arise in the context of other communications, including other Physical Downlink Shared Channel (PDSCH) transmissions or other Physical Uplink Shared Channel (PUSCH) transmissions.

[0072] For robust decoding of such messages, a low coding rate can be implemented (e.g., a more robust MCS associated with a low code rate). A low code rate can be associated with increased redundancy (e.g., repeated information bits), which can provide more robust transmission in the presence of interference. In some examples, the base station and UE can access an MCS table to determine the MCS used for uplink and downlink transmission. However, in some scenarios (e.g., during random access message exchange), alternative MCSs (e.g., MCSs not included or listed in the default MCS table) may be desired. For example, the lowest MCS used for the Physical Downlink Shared Channel (PDSCH) could be associated with a lower coding rate. The code rate corresponds to a Quadrature Phase Shift Keying (QPSK) modulation scheme. According to the techniques described herein, alternative MCSs (e.g., lower MCSs, MCSs not included in the default MCS table, etc.) can be determined and signaled between radio devices. Specifically, these techniques can be implemented during random access message exchanges (e.g., base station transmissions for RAR, UE transmissions for RRC connection requests (Random Access Msg3), etc.).

[0073] In some cases, the base station may indicate an alternative MCS to the UE during the random access procedure (e.g., a combination of modulation schemes, code rates, transport block sizes (TBS), available resource elements (REs) used for TBS determination, spatial streams, etc., not included in the default MCS table). For example, downlink control information (DCI) scrambled with a random access radio network temporary identifier (RA-RNTI) may include one or more indications of an alternative MCS for subsequent RAR messages (e.g., reserved bits or reserved fields of the RA-RNTI scrambled DCI may include information indicating an alternative MCS). Generally, DCI scrambled with any RNTI (e.g., system information RNTI (SI-RNTI), paging RNTI (P-RNTI), etc.) may include an indication of an alternative MCS for subsequent PDSCHs (e.g., broadcast PDSCHs scheduled by the DCI of the physical downlink control channel (PDCCH)). Additionally or alternatively, downlink messages (e.g., RAR messages) may include indications of alternative MCSs for subsequent uplink transmissions (e.g., RRC connection request messages). (For example, reserved bits or reserved fields in RAR messages may include information indicating alternative MCSs.)

[0074] In some implementations, the indication of an alternative MCS may include an indication of an MCS scaling factor. The indicated MCS scaling factor may be applied to a value in the default MCS table (e.g., the lowest MCS value or some other MCS value indicated via other reserved bits) to determine an alternative MCS (e.g., an alternative transport block size corresponding to an alternative coding rate). For example, a base station may indicate a scaling factor in the reserved (e.g., unused, or in some cases repurposed) field of a RA-RNTI-scrambled DCI to indicate the desired alternative MCS. The UE may receive the DCI message, determine the association of the DCI message with a random access procedure (e.g., RAR) based on the RNTI used to decode the DCI (e.g., based on RA-RNTI scrambling), and identify the scaling factor indicated in the reserved field of the DCI. That is, the reserved field of the RA-RNTI-scrambled DCI may indicate the scaling factor to be applied to the MCS indicated by the DCI (e.g., in the MCS field of the DCI). Accordingly, the indicated alternative MCS may include a lower code rate than that provided in the default MCS table (e.g., when the scaling factor is applied to the lowest default MCS) for more robust random access communication. Additional alternative MCSs with increased granularity may be selected compared to the MCSs provided in the default MCS table (e.g., when the scaling factor is applied to other indicated MCS values ​​in the default MCS table).

[0075] Additionally or alternatively, the alternative MCS indication may include an indication of using an alternative MCS table (e.g., where the alternative MCS can be identified from the indicated alternative MCS table). For example, a base station may indicate an MCS index corresponding to an alternative MCS table in a RA-RNTI scrambled DCI to indicate the desired alternative MCS. In some cases, reserved (e.g., unused, or in some cases, repurposed) fields of the RA-RNTI scrambled DCI may indicate the use of an alternative MCS table, and the MCS field of the DCI may indicate an MCS index associated with the alternative MCS table. In other examples, reserved fields of the RA-RNTI scrambled DCI may directly indicate an MCS index of the alternative MCS table (e.g., reserved fields of the RA-RNTI scrambled DCI may include an alternative MCS index that implicitly indicates the use of an alternative MCS table).

[0076] The alternative MCS indication techniques discussed above can also be applied to other transmissions (e.g., they can be included in RAR messages), as further described below. Advantageously, these techniques can provide a lower MCS (e.g., a lower coding rate and / or a lower modulation order) than the MCS additionally provided in the default MCS table. Furthermore, since new MCS tables (e.g., alternative MCS tables) can be defined and indicated, MCS can be configured and implemented with increased flexibility, as the wireless communication system gains support for additional MCS by using the techniques described herein.

[0077] First, aspects of this disclosure are described within the context of a wireless communication system. Then, the processing flow for implementing the described alternative MCS signaling technology is discussed. These aspects of the disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to the signaling of the alternative MCS.

[0078] Figure 1 An example of a wireless communication system 100 supporting signaling for alternative MCSs according to various aspects of this disclosure is illustrated. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 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. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices.

[0079] Base station 105 can wirelessly communicate with UE 115 via one or more base station antennas. Base station 105 described herein may include, or may be referred to by those skilled in the art as, a base station transceiver, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation Node B or gigabit nodeB (any of which may be referred to as gNB), home NodeB, home eNodeB, or other suitable terms. Wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). UE 115 described herein can communicate with various types of base stations 105 and network devices, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0080] Each base station 105 may be associated with a specific geographic coverage area 110, within which communication with each UE 115 is supported. Each base station 105 may provide communication coverage to the corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 may include uplink transmission from the UE 115 to the base station 105, or downlink transmission from the base station 105 to the UE 115. Downlink transmission may also be referred to as forward link transmission, and uplink transmission may also be referred to as reverse link transmission.

[0081] The geographic coverage area 110 of base station 105 can be divided into sectors that constitute only a part of the geographic coverage area 110, and each sector can be associated with a cell. For example, each base station 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, base station 105 can be mobile and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and overlapping geographic coverage areas 110 associated with different technologies can be supported by the same base station 105 or different base stations 105. Wireless communication system 100 can include, for example, heterogeneous LTE / LTE-A / LTE-A Pro or NR networks, wherein different types of base stations 105 provide coverage for various geographic coverage areas 110.

[0082] The term "cell" refers to a logical communication entity used to communicate with base station 105 (e.g., via a carrier) and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish neighboring cells operating via the same or different carriers. In some examples, a carrier may support multiple cells and may be configured with different cell types based on different protocol types that can provide access to different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographical coverage area 110 on which the logical entity operates.

[0083] UE 115 (e.g., eMBB UE 115) may be distributed throughout the wireless communication system 100, and each UE 115 may be fixed or mobile. UE 115 may also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client. UE 115 may also be a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may also refer to a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device, which can be implemented in various items such as appliances, vehicles, meters, etc.

[0084] Some UEs 115, such as MTC or IoT devices, can be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application that can utilize the information or present it to people interacting with the program or application. Some UEs 115 can be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0085] Some UEs 115 can be configured to operate in reduced power consumption modes, such as half-duplex communication (e.g., a mode supporting unidirectional communication via transmission or reception, but not simultaneously). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving "deep sleep" mode when not engaged in active communication or operating on limited bandwidth (e.g., according to narrowband communication). In some cases, UE 115 can be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 can be configured to provide ultra-reliable communication to these functions.

[0086] In some cases, UE 115 may also be able to communicate directly with other UE 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more UEs in a group of UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115 in the group may be outside the geographic coverage area 110 of base station 105, or in other cases, may not be able to receive transmissions from base station 105. In some cases, the group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to every other UE 115 in the group. In some cases, base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UEs 115 without the involvement of base station 105.

[0087] Base station 105 can communicate with core network 130 and can communicate with each other. For example, base station 105 can interface with core network 130 via backhaul link 132 (e.g., via S1 or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130) via backhaul link 134 (e.g., via X2 or other interfaces).

[0088] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC), which may include at least one Mobility Management Entity (MME), at least one Serving Gateway (S-GW), and at least one Packet Data Network (PDN) Gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with the EPC. User IP packets can be delivered through the S-GW, which itself can connect to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can connect to network operator IP services. Operator IP services may include access to the Internet, one or more intranets, IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.

[0089] At least some of the network devices, such as base station 105, may include sub-components such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity may communicate with UE 115 through multiple other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or combined into a single network device (e.g., base station 105).

[0090] Wireless communication system 100 can operate using one or more frequency bands typically in the 300MHz to 300GHz range. Generally, the region from 300MHz to 3GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because wavelength distances range from approximately 1 decimeter to 1 meter. Building and environmental features may block or redirect UHF waves. However, the waves can penetrate structures sufficiently to provide service from a macrocell to an indoor UE 115. Compared to transmissions using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300MHz, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100km).

[0091] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using the 3 GHz to 30 GHz frequency band, also known as the centimeter band. The SHF region includes frequency bands such as the 5 GHz Industrial, Scientific and Medical (ISM) band, which can be used as appropriate by devices that can tolerate interference from other users.

[0092] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the individual devices can be even smaller and more closely spaced than UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 115. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater atmospheric attenuation and shorter range. The techniques disclosed herein can be employed between transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary by country or regulatory body.

[0093] In some cases, wireless communication system 100 may utilize both licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz ISM band. When operating in unlicensed radio spectrum bands, wireless devices such as base station 105 and UE 115 may employ a pre-call listening (LBT) procedure to ensure that the frequency channel is open before transmitting data. In some cases, operation in unlicensed bands may be based on CA configuration along with CC operation in licensed bands (e.g., LAA). Operation in unlicensed spectrum may include downlink transmission, uplink transmission, peer-to-peer transmission, or a combination of these transmissions. Duplexing in unlicensed spectrum may be based on Frequency Division Duplex (FDD), Time Division Duplex (TDD), or a combination of both.

[0094] In some examples, base station 105 or user equipment 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output communication, or beamforming. For example, wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. Multiple-input multiple-output (MIMO) communication can employ multipath signal propagation, improving spectral efficiency by transmitting or receiving multiple signals via different spatial layers; this can be referred to as spatial multiplexing. For example, multiple signals may be transmitted by the transmitting device via different antennas or different combinations of antennas. Similarly, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0095] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals that communicate via antenna elements in an antenna array, such that signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustment of signals communicating via antenna elements can include the transmitting or receiving device applying a certain amplitude and phase offset to the signal carried via each antenna element associated with that device. The adjustment associated with each antenna element can be defined by a beamforming weight set associated with a specific direction (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other direction).

[0096] In one example, base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions, which may include signals transmitted according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions can be used to identify (e.g., by base station 105 or a receiving device such as UE 115) beam directions for subsequent transmissions and / or receptions performed by base station 105. Base station 105 may transmit some signals, such as data signals, associated with a specific receiving device in a single beam direction (e.g., the direction associated with a receiving device such as UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined at least in part based on the signals transmitted in different beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal it received with the highest signal quality or otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam direction for subsequent transmissions or receptions by UE 115), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0097] A receiving device (e.g., UE 115, an example of a millimeter-wave (mmW) receiving device) may attempt multiple receive beams when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signals according to different antenna subarrays; receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array; or processing the received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these can be referred to as "listening" depending on the different receive beams or receiving directions. In some examples, the receiving device may use a single receive beam along a single beam direction (e.g., when receiving data signals). A single receiving beam can be aligned at least in part based on a beam direction determined by listening to different receiving beam directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening to multiple beam directions).

[0098] In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna fitting, such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with multiple rows and columns of antenna ports, which base station 105 may use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations.

[0099] In some cases, the wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. In some cases, the Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The Media Access Control (MAC) layer may perform priority processing and multiplex logical channels into transport channels. The MAC layer may also provide retransmission at the MAC layer using Hybrid Automatic Repeat Request (HARQ) to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 that supports radio bearers for user plane data. At the physical (PHY) layer, transport channels may be mapped to physical channels.

[0100] In some cases, UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique to increase the likelihood of correctly receiving data through communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under adverse radio conditions (e.g., signal-to-noise ratio conditions). In some cases, the radio device can support HARQ feedback within the same time slot, where the device can provide HARQ feedback in a specific time slot for data received in a previous symbol within that time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0101] In LTE or NR, time intervals can be expressed as multiples of the basic time unit, for example, they can refer to T. s= 1 / 30720000 seconds of sampling period. The time interval of communication resources can be organized according to radio frames, each with a duration of 10 milliseconds (ms), where the frame period can be expressed as T. f =307200T s Radio frames can be identified by System Frame Numbers (SFNs) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. Subframes may also be divided into two time slots, each with a duration of 0.5 ms, and each time slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In addition to the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the minimum scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs) or in selected component carriers using sTTIs).

[0102] In some wireless communication systems, time slots can be further divided into multiple mini-slots containing one or more symbols. In some cases, a symbol or mini-slot can be the smallest unit of scheduling. For example, the duration of each symbol can vary depending on the subcarrier spacing or operating frequency band. Additionally, some wireless communication systems can implement time slot aggregation, where multiple time slots or mini-slots are aggregated together and used for communication between UE 115 and base station 105.

[0103] The term "carrier" refers to a collection of radio spectrum resources with a defined physical layer structure for supporting communications via communication link 125. For example, a carrier of communication link 125 may include a portion of a radio spectrum band operating according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. Carriers may be associated with predefined frequency channels (e.g., E-UTRA Absolute Radio Channel Number (EARFCN)) and can be located according to a channel grid for discovery by UE 115. Carriers may be downlink or uplink (e.g., in FDD mode), or configured to carry both downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted via a carrier may consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

[0104] The carrier organization structure can differ depending on the radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR, etc.). For example, communication on a carrier can be organized according to TTIs or time slots, each TTI or time slot including user data and control information or signaling used to support the decoding of the user data. A carrier can also include dedicated acquisition signaling (e.g., synchronization signals or system information) and control signaling coordinating the operation of the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition or control signaling coordinating the operation of other carriers.

[0105] Physical channels can be multiplexed on a carrier using various techniques. For example, time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. In some examples, control information transmitted in the physical control channel can be distributed in a concatenated manner between different control regions (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

[0106] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth can be one of several predetermined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 can be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predefined portion or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., “in-band” deployment of a narrowband protocol type).

[0107] In systems employing MCM technology, a resource element can consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely proportional. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate UE 115 can achieve. In MIMO systems, wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers can further increase the data rate of communication with UE 115.

[0108] The devices of the wireless communication system 100 (e.g., base station 105 or UE 115) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include base station 105 and / or UE 115, which may support simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0109] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers; this feature can be referred to as carrier aggregation (CA) or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 can be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation can be used with both FDD and TDD component carriers.

[0110] In some cases, the wireless communication system 100 may utilize enhanced component carrier (eCC). eCC can be characterized by one or more features, including wider carrier or frequency channel bandwidth, shorter symbol duration, shorter TTI duration, or a modified control channel configuration. In some cases, eCC may be associated with carrier aggregation or dual connectivity configurations (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). eCC can also be configured for use in unlicensed or shared spectrum (e.g., where more than one operator is permitted to use the spectrum). eCC characterized by wide carrier bandwidth may include one or more frequency bands that UE 115 cannot utilize, that UE 115 cannot monitor the entire carrier bandwidth, or that are otherwise configured to use limited carrier bandwidth (e.g., to conserve power).

[0111] In some cases, eCC can utilize a different symbol duration than other CCs, which may include using a reduced symbol duration compared to other CCs. A shorter symbol duration can be associated with an increased spacing between adjacent subcarriers. Devices utilizing eCC (such as UE 115 or base station 105) can transmit wideband signals (e.g., based on frequency channels or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). The TTI in eCC can consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) can be variable.

[0112] Wireless communication systems such as NR systems can utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility in eCC symbol duration and subcarrier spacing allows eCC to be used across multiple spectrums. In some examples, NR spectrum sharing can improve spectrum utilization and efficiency, specifically through dynamic vertical (e.g., across frequency domains) and horizontal (e.g., across time domains) resource sharing.

[0113] UE 115, accessing the network, can receive discovery signaling, such as synchronization signals, Master Information Block (MIB), First System Information Block (SIB1), and Second System Information Block (SIB2). For example, SIB1 may contain cell access parameters and scheduling information for other SIBs. Decoding SIB1 enables UE 115 to receive SIB2. SIB2 may contain RRC configuration information related to RACH procedures, paging, Physical Uplink Control Channel (PUCCH), PUSCH, power control, SRS, and cell barring.

[0114] After UE 115 decodes SIB2, it can send a RACH preamble to base station 105. This can be referred to as RACH message 1. For example, the RACH preamble can be randomly selected from a set of 64 predetermined sequences. This allows base station 105 to distinguish between multiple UEs 115 attempting to access the system simultaneously. Base station 105 can respond with a Random Access Response (RAR) or RACH message 2, which provides uplink resource grant, timing advance, and temporary cell radio network temporary identifier (C-RNTI).

[0115] Then, UE 115 can send an RRC connection request or RACH message 3, along with a Temporary Mobile Subscriber Identifier (TMSI) (if UE 115 has previously connected to the same wireless network) or a random identifier. The RRC connection request can also indicate the reason for UE 115's connection to the network (e.g., emergency, signaling, data exchange, etc.). Base station 105 can respond to the connection request with a contention resolution message or RACH message 4 addressed to UE 115, which can provide a new C-RNTI. If UE 115 receives a contention resolution message with the correct identifier (ID), it can proceed with RRC setup. If UE 115 does not receive a contention resolution message (e.g., if there is a conflict with another UE 115), it can repeat the RACH process by sending a new RACH preamble. In some cases, a small amount of data can be sent in RACH message 1 or 2, or both, and UE 115 can remain idle instead of establishing a radio connection after receiving RACH message 2.

[0116] In some cases, UE 115 can enter idle mode and periodically wake up to receive paging messages. In some cases, a Paging Radio Network Temporary Identifier (P-RNTI) can be assigned to UE 115 in idle mode. If the Serving Gateway (S-GW) receives data from UE 115, it can notify the Mobility Management Entity (MME), which can then send paging messages to each base station 105 within an area known as the tracking area. Each base station 105 within the tracking area can send a paging message with the P-RNTI. Therefore, the UE can remain idle without updating the MME until it leaves the tracking area. In some cases, a shortened local paging ID can be used for UE 115 that does not frequently move from one location to another (e.g., for MTC UE 115, such as fixed surveillance equipment).

[0117] Base station 105 or UE 115, or both, can convey data in control messages, such as Physical Downlink Control Channel (PDCCH) or Physical Uplink Control Channel (PUCCH) messages. The PDCCH carries downlink control information (DCI) in control channel elements (CCEs), which can consist of nine logically contiguous resource element (RE) groups (REGs), where each REG contains four resource elements (REs). Resource elements can include a single symbol period on a single tone. The DCI includes information about downlink scheduling assignment, uplink resource allocation, transmission schemes, uplink power control, Hybrid Automatic Repeat Request (HARQ) information, MCS information, and other information.

[0118] The size and format of DCI messages can vary depending on the type and amount of information carried by the DCI. For example, if spatial multiplexing is supported, the DCI message size will be larger compared to continuous frequency allocations. Similarly, for systems employing MIMO, the DCI must include additional signaling information. The size and format of the DCI depend on the amount of information and factors such as bandwidth, the number of antenna ports, and the duplex mode.

[0119] The PDCCH can carry DCI messages associated with multiple users, and each UE 115 can decode the DCI message for itself. For example, a C-RNTI can be assigned to each UE 115, and the CRC bits appended to each DCI can be scrambled based on the C-RNTI. To reduce power consumption and overhead at the UE, a restricted set of CCE locations can be specified for the DCI associated with a particular UE 115. CCEs can be grouped (e.g., into groups of 1, 2, 4, and 8 CCEs), and a set of CCE locations in which the UE can find the associated DCI can be specified. These CCEs can be referred to as the search space.

[0120] Base station 105 and UE 115 may employ techniques for indicating alternative MCSs (e.g., MCS values ​​or MCS indexes unrelated to the default list or default MCS table). That is, communications (e.g., physical downlink control channel (PDCCH) transmission carrying downlink control information (DCI), physical downlink shared channel (PDSCH) transmission carrying uplink clearance, etc.) may include information indicating alternative MCSs (e.g., in the MCS field and reserved fields) for subsequent communications. For example, a DCI scrambled with a random access radio network temporary identifier (RA-RNTI), random access response (RAR) message, etc., may indicate an alternative MCS for subsequent messages during the random access process (e.g., for RAR, RRC connection request, etc.). An alternative MCS can be conveyed by including in the transmitted reserved fields an indication of information such as an MCS scaling factor, the ID of the alternative MCS table, an MCS index associated with the alternative MCS table, or some combination thereof.

[0121] Figure 2 An example of a wireless communication system 200 supporting signaling for an alternative MCS according to various aspects of this disclosure is illustrated. In some examples, the wireless communication system 200 may implement various aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be referenced... Figure 1 Examples of corresponding devices described. Base station 105-a can provide network coverage for geographic area 110-a. Base station 105-a can signal alternative MCS values ​​(e.g., MCS values ​​not listed or included in the default MCS table) to UE 115-a via downlink transmission 205. In some examples, downlink transmission 205 indicating alternative MCS values ​​may include header field 210, MCS field 215, and one or more reserved fields 220. For example, base station 105-a and UE 115-a can participate in a random access procedure to establish an RRC connection, as described above. Figure 1Further description. As described in more detail below, base station 105-a may signal an alternative MCS value (e.g., 205 transmitted via downlink) for UE 115-a to use during random access message exchange (e.g., for UE 115-a to receive RAR, for UE 115-a to send RRC connection requests, etc.).

[0122] In some examples, base station 105-a and UE 115-a may exchange messages (e.g., data, control, RACH messages) on a communication link (e.g., communication link 125). To establish a communication link, UE 115-a (e.g., in some cases it may be an eMBB UE 115) may attempt to acquire a cell served by base station 105-a by sending a random access message (e.g., a random access preamble or random access Msg1) to base station 105-a. The random access message may include a RACH preamble that may be included in the physical RACH (PRACH) signal, and a random access radio network temporary identifier (RA-RNTI) associated with UE 115-a. After receiving the RACH message from UE 115-a, base station 105-a may send a RAR (e.g., a RAR message or random access Msg2) to UE 115-a. The RAR may include a temporary cell RNTI (C-RNTI) that base station 105-a can use to identify UE 115-a. The RAR may also include uplink license resources for UE 115-a. UE 115-a can use the uplink license resources to send an RRC connection request message (e.g., random access Msg3) to base station 105-a to establish an RRC connection with base station 105-a. In response to the RRC connection request message, base station 105-a can send an RRC connection establishment message (e.g., random access Msg4) to UE 115-a, which completes the random access procedure.

[0123] In some implementations, base station 105-a and UE 115-a can communicate using beamforming or directional transmission. For example, base station 105-a can transmit downlink transmission 205 via downlink beam 225, and UE 115-a can transmit uplink transmission via uplink beam 230. For example, beamforming transmission can be used to mitigate path loss associated with high-frequency communication. That is, base station 105-a and UE 115-a can include multiple antennas, and various antenna configurations can be used to transmit and receive signals to achieve directional transmission and / or reception.

[0124] In some cases (e.g., during initial cell acquisition), the beams used for transmission (e.g., beams 225, 230) may not be well refined (e.g., due to the lack of an established RRC connection, the lack of a beam refinement process, etc.). For example, base station 105-a may transmit an SSB carrying a system information block (e.g., including information such as cell ID, common and shared channel information, RRC uplink power control, cyclic prefix length, etc.) for cell access of UE 115-a. UE 115-a may monitor the SSB and may initiate a random access procedure (e.g., a random access channel (RACH) procedure, a physical RACH (PRACH) procedure, etc.) to establish an RRC connection with base station 105-a. Due to the lack of an established RRC connection (e.g., the lack of a beam refinement process, prior to the communication of channel and transmission parameters, etc.), messages exchanged during the random access procedure may suffer from low SNR, high carrier frequency offset, etc. For example, beamforming and frequency synchronization associated with RAR (e.g., Msg2) or RRC connection requests (e.g., Msg3) may not be refined, and RAR may be associated with low SNR and / or high carrier frequency offset because timing and carrier frequency information may not be well synchronized. Similar problems may arise in the context of other communications, including other PDSCH transmissions.

[0125] For robust decoding of such messages, a low coding rate can be implemented (e.g., a more robust MCS associated with a low code rate). A low code rate can be associated with increased redundancy (e.g., repeated information bits), which can provide more robust transmission in the presence of interference. In some examples, the base station and UE can access an MCS table to determine the MCS used for uplink and downlink transmission. However, in some scenarios (e.g., during random access message exchange), alternative MCSs (e.g., MCSs not included or listed in the default MCS table) may be desired. For example, the lowest default MCS for PDSCH could be a MCS with… The corresponding QPSK modulation scheme corresponds to the code rate. According to the techniques described herein, alternative MCSs (e.g., lower MCSs, MCSs not included in the default MCS table, etc.) can be determined and signaled between base station 105-a and UE 115-a. As a concrete example, these techniques can be implemented during random access message exchange (e.g., base station 105-a sending for RAR, UE 115-a, etc. for RRC connection request (random access Msg3)).

[0126] Wireless communication system 200 may employ techniques for indicating alternative MCSs (e.g., MCS values ​​or MCS indices not included in the default list or default table). That is, using the techniques described below, communication (e.g., downlink transmission 205) may include information (e.g., one or more reserved bits in reserved field 220) indicating alternative MCSs not in the default or pre-configured MCS tables. Downlink transmission 205 (e.g., RA-RNTI scrambled DCI, RAR, etc.) may indicate alternative MCSs (e.g., for RAR, RRC connection requests, etc.) by indicating that the MCS index associated with the alternative MCS is not in the default table, by indicating a scaling factor, by indicating the ID of a new MCS table, by indicating the MCS index associated with the alternative MCS table, or some combination thereof, as discussed below. PDCCH transmission may carry a DCI including an indication of the alternative MCS to be used in subsequent PDSCH transmissions (e.g., for RAR or random access Msg2 transmissions). In some cases, PDSCH transmissions (e.g., RAR or Random Access Msg2 transmissions) may also carry an indication of an alternative MCS to be used in subsequent PUSCH transmissions (e.g., uplink RRC connection request messages).

[0127] In some cases, base station 105-a may indicate an alternative MCS to the UE during the random access procedure (e.g., a combination of modulation schemes, code rates, TBS, available REs for TBS determination, spatial streams, etc., not included in the default MCS table). For example, a downlink DCI scrambled with RA-RNTI (e.g., downlink transmission 205) may include an indication of an alternative MCS for subsequent RAR messages (e.g., reserved bits or reserved fields 220 of the RA-RNTI scrambled DCI may include information indicating an alternative MCS). Generally, a DCI scrambled with any RNTI (e.g., SI-RNTI, P-RNTI, etc.) may include an indication of an alternative MCS for subsequent PDSCHs (e.g., broadcast PDSCHs scheduled by the DCI of the PDCCH). Additionally or alternatively, RAR messages (e.g., downlink transmission 205) may include an indication of an alternative MCS for subsequent RRC connection request messages (e.g., reserved bits or reserved fields 220 of the RAR message may include information indicating an alternative MCS).

[0128] In some implementations, the indication of an alternative MCS may include an indication of an MCS scaling factor. The indicated MCS scaling factor may be applied to a value in the default MCS table (e.g., the lowest MCS value or some other MCS value indicated via other reserved bits) to determine the alternative MCS. For example, base station 105-a may indicate a scaling factor in a reserved field 220-a of a RA-RNTI-scrambled DCI to indicate a desired alternative MCS. UE 115-a may receive a DCI message (e.g., downlink transmission 205), determine the association of the DCI message with a random access procedure (e.g., RAR) based on the RNTI used to decode the DCI (e.g., based on RA-RNTI scrambling), and identify the scaling factor indicated in the reserved field 220-a of the DCI. That is, the reserved field 220-a of the RA-RNTI-scrambled DCI may indicate a scaling factor to be applied to the MCS indicated by the DCI (e.g., in the MCS field 215 of the DCI). Therefore, the indicated alternative MCS may include a lower code rate than that provided in the default MCS table (e.g., when the scaling factor is applied to the lowest default MCS (such as MCS0)) for more robust random access communication. As another example, as part of determining the alternative TBS, an MCS scaling factor may be applied to the code rate in the default MCS table. In some cases, the RA-RNTI scrambled DCI may also include an indication of the MCS index (e.g., such as MCS1, MCS2, etc.) of the MCS to apply the scaling factor (e.g., overriding the default assumption to multiply the scaling factor by the lowest MCS in the default table). For example, reserved field 220-a of the RA-RNTI scrambled DCI may indicate the scaling factor, while reserved field 220-b of the RA-RNTI scrambled DCI may indicate the MCS index associated with the default MCS table, such that the alternative MCS can be determined by multiplying the scaling factor by the MCS associated with the MCS index indicated by reserved field 220-b. Therefore, compared to the MCS provided in the default MCS table, you can configure or select an MCS with increased granularity.

[0129] For example, UE 115-a can determine the alternative MCS (e.g., the actual transmitted MCS) by multiplying the scaling factor identified in reserved field 220-a by the lowest MCS in the default MCS table, or in some cases by the MCS associated with the MCS index of the default MCS table identified in reserved field 220-b. Reserved field 220-a can use a certain number of bits to indicate the scaling factor (e.g., reserved field 220-a may include 3 bits), where the scaling factor can be identified as the inverse multiplication of the decimal value N represented by these bits. That is, the three-bit reserved field 220-a can indicate the decimal value N = 0, 1, 2, 3, 4, 5, 6, or 7, and the scaling factor indicated by the three bits of reserved field 220-a can respectively include... or Accordingly, reserved field 220-a can be set to "011" to indicate the scaling factor. In some examples, reserved field 220-a can be set to a decimal value of 0 or 1 (e.g., “000” or “001” respectively) to indicate that the default table should be used and that no scaling factor will be applied (e.g., UE 115-a can obtain the MCS from the default table as indicated by the MCS field 215).

[0130] Accordingly, base station 105-a can use bits of MCS field 215 and reserved field 220 to indicate the alternative MCS. For example, the lowest MCS used for PDSCH can be associated with... The code rate corresponds to the QPSK modulation scheme. Base station 105-a may include a reserved bit field 220-a set to "010" in the RA-RNTI scrambled DCI to indicate that it has... Alternative MCS to the QPSK modulation scheme of the code rate. The techniques described above are discussed for application in DCI message transmission and reception to set the MCS for Msg2 for random access procedures. However, these techniques are equally applicable to indications sent in downlink messages such as Msg2 (e.g., RAR transmission) to set the MCS for uplink transmissions such as Msg3 for random access procedures (e.g., as per [reference to...]). Figure 4(Further discussion follows). For example, reserved bits (e.g., reserved field 220) can be used to add a scaling factor to the MCS field 215 (e.g., the truncated MCS field of Msg2) in the RAR payload (e.g., Msg2) to indicate the alternative MCS for Msg3. Furthermore, the above techniques are discussed in the context of scaling the code rate associated with the MCS. Similarly, the above techniques can also be applied to other MCS parameters (e.g., modulation scheme, TBS, number of OFDM symbols used for TBS determination, number of spatial streams, etc.) without departing from the scope of this disclosure. For example, scaling can be applied to the modulation scheme (e.g., QPSK multiplied by...). The scaling factor can indicate binary phase shift keying (BPSK) modulation, TBS index (e.g., the scaling factor can be applied to the TBS), etc. As an additional example, scaling can be applied to the bitrate in the default MCS table as part of an alternative TBS determination.

[0131] Additionally or alternatively, the indication of an alternative MCS may include an indication of using an alternative MCS table (e.g., where the alternative MCS can be identified from the indicated alternative MCS table). For example, base station 105-a may indicate an MCS index corresponding to an alternative MCS table in the RA-RNTI scrambled DCI to indicate the desired alternative MCS (e.g., the actual transmission MCS for Msg2). In some cases, the reserved field 220-a of the RA-RNTI scrambled DCI may indicate the use of an alternative MCS table, and the MCS field 215 of the DCI may indicate an MCS index associated with the alternative MCS table. For example, the reserved field 220-a may include a single toggle bit indicating the alternative MCS table to be used for MCS determination (e.g., the alternative table may be predefined or associated with a random access procedure and can be indicated by setting the toggle bit in the reserved field 220-a). In other cases (e.g., where multiple MCS tables may be used), reserved field 220-a may include a multi-bit indicator (e.g., 2 bits) that indicates the index associated with the alternative MCS table to be used for MCS determination. Reserved field 220-a may be used in conjunction with MCS field 215 (e.g., which may indicate the MCS index associated with the table indicated by reserved field 220-a) to indicate the alternative MCS.

[0132] In other examples, the reserved field 220-a of the RA-RNTI scrambled DCI can directly indicate the MCS index of the alternative MCS table (e.g., the reserved field of the RA-RNTI scrambled DCI can include an alternative MCS index that implicitly indicates the use of the alternative MCS table). That is, the reserved field 220-a can include multiple bits (e.g., 5 bits) and can indicate the MCS index that identifies the alternative MCS in the alternative MCS table. In some cases, the MCS field 215 can be set to the value "00000" to indicate that the alternative MCS table should be used (e.g., this could prompt the receiving device to recognize that the reserved field 220-a has an MCS index corresponding to the new / alternative MCS table). Alternatively, the reserved field 220-a, including the bit value "00000", can indicate that the default table should be used (e.g., to use the default MCS table and MCS field 215 to determine the MCS). In other cases, reserved field 220-a may include the bit value "00011", which indicates that a third MCS value associated with the alternative MCS table can be used to determine the alternative MCS (e.g., a non-null or non-zero value in reserved field 220-a may implicitly indicate that a non-default MCS table should be used, and the bit value may indicate the MCS index associated with the non-default MCS table). In some examples (e.g., in scenarios where several MCS tables can be defined), reserved field 220-a may indicate the MCS index that identifies the alternative MCS in the alternative MCS table, and reserved field 220-b may indicate the alternative MCS table to be used with the MCS index.

[0133] For reference Figure 4 Furthermore, the alternative MCS indication techniques discussed above can also be applied to other transmissions (e.g., they can be included in RAR messages). For example, a combination of reserved field 220 and MCS field 215 (e.g., the truncated MCS field of Msg2) can be included in Msg2 for alternative MCS indication of Msg3. Advantageously, these techniques can provide an MCS lower than the MCS additionally provided in the default MCS table. Moreover, since new MCS tables (e.g., alternative MCS tables) can be defined and indicated, MCS can be configured and implemented with increased flexibility, as the wireless communication system gains support for additional MCS by using the techniques described herein.

[0134] According to other implementations, the signaling of the alternative MCS may include signaling for determining the number of OFDM symbols, REs, RBs, etc., for the TBS. That is, in some cases, the indication of the alternative MCS may include an indication of the number of OFDM symbols that can be used for TBS determination. For example, base station 105-a may indicate the number of OFDM symbols in reserved field 220-a of RA-RNTI scrambled DCI. UE 115-a may receive DCI messages (e.g., downlink transmission 205), determine the association of the DCI message with a random access procedure (e.g., RAR) based on the RNTI used to decode the DCI (e.g., based on RA-RNTI scrambling), and identify the number of OFDM symbols indicated in reserved field 220-a of the DCI. That is, reserved field 220-a of RA-RNTI scrambled DCI may indicate the number of OFDM symbols used to determine the TBS of Msg2.

[0135] UE 115-a can receive RB allocation (e.g., via DCI included in downlink transmission 205) and the number of OFDM symbols (e.g., indicated via reserved field 220-a). For example, MCS0 can be assumed or defaulted to a 24RB 12 OFDM symbol allocation. If reserved field 220-a includes an indication of 2 OFDM symbols (e.g., reserved field 220-a indicates the bit value of "00010"), then UE 115-a can use this indication for TBS determination. UE 115-a can then process (e.g., for RA-RNTI) PDSCH on all 24 RBs and 12 OFDM symbols, but the TBS value can be derived as... To determine an approximate 56-bit payload, UE 115-a can then repeat the encoded TBS over the remaining 10 OFDM symbols to fill the entire 12 OFDM symbol allocation. For example, the RAR (Msg2) sent from base station 105-a to UE 115-a in response to the random access preamble (Msg1) may include a fixed payload (e.g., a fixed payload of 56 bits per UE 115).

[0136] As another example, UE 115-a can determine TBS according to the following scheme. UE 115-a can first determine the number of REs (N) within the time slot. RE (For example, in some cases, base station 105-a may indicate N in reserved field 220) RE UE 115-a can use equations. To determine the number (N′) of REs allocated for PDSCH within a Physical Resource Block (PRB). RE ),in This is the number of subcarriers in the physical resource block (e.g., 12); It is the number of symbols (e.g., OFDM symbols) allocated by PDSCH within the time slot (e.g., 14 or 12); This refers to the number of REs used per PRB for demodulation reference signal (DM-RS) during the scheduling duration, including the overhead of the DM-RS code division multiplexing (CDM) group indicated by DCI format 1_0 / 1_1; and This is the overhead configured by the higher-layer parameter Xoh-PDSCH. If Xoh-PDSCH is not configured (e.g., a value from 0, 6, 12, or 18), then Xoh-PDSCH can be set to 0. UE 115-a can determine the total number of REs allocated to PDSCH (e.g., N). RE Through N RE =(156,N′) RE )*n PRB ), where n PRB This is the total number of PRBs allocated for UE 115-a. Next, it can be determined through N... info =N RE *R*Q m *v Obtains the intermediate number (N) of information bits. info ), where R is the bit rate; Q m It is the modulation format (e.g., 2 for QPSK, 4 for 14QAM, etc.); and v is the number of layers. It can be derived from N. info The TBS size is determined (e.g., via a combination of equations and mappings to tables). For a PDSCH communicated via a scrambled PDCCH such as SI-RNTI, RA-RNTI, etc., N can be... info Differently determined as N info =N RE *R*Q m *v*ScalingFactor, where the scaling factor (or an indication of the scaling factor) can be carried by reserved bits in the DCI.

[0137] In some cases, the alternative MCS table may refer to a table defined by Msg2, Msg3, or both (e.g., defined for the RACH procedure). Furthermore, the alternative MCS, and the signaling and determination of the alternative MCS, may refer to any combination of the aforementioned techniques (e.g., alternative / lower code rate, reduced modulation scheme, indicated OFDM symbol for determining the alternative TBS, etc.).

[0138] In some implementations, the DCI (e.g., communicated in downlink transmission 205) may indicate an alternative MCS (e.g., an MCS value not included or listed in the default table) for the scheduled RAR. That is, the DCI may schedule the RAR and may indicate an alternative MCS that base station 105-a will use to transmit the RAR. For example, the DCI may include an MCS field 215 and one or more reserved fields 220 (e.g., reserved bits). The MCS field 215 and one or more reserved fields 220 may together indicate the alternative MCS. According to the described techniques, the DCI may include a scaling factor and an indication of the MCS value in the default table, or an indication of an MCS index associated with a second non-default table, to indicate an alternative MCS (e.g., which may be used by base station 105-a to transmit subsequent RARs).

[0139] Additionally or alternatively, (e.g., communicated in downlink transmission 205) the RAR may indicate an alternative MCS (e.g., an MCS value not included or listed in the default table) for the scheduled RRC connection request. That is, the RAR includes an uplink grant for the RRC connection request and may indicate an alternative MCS for UE 115-a to use in transmitting the RRC connection request. For example, the RAR may include an MCS field 215 (e.g., a truncated MCS field) and one or more reserved fields 220 (e.g., reserved bits). The MCS field 215 and one or more reserved fields 220 may together indicate the alternative MCS. According to the described techniques, the RAR may include a scaling factor and an indication of the MCS value in the default table, or an indication of an MCS index associated with a second non-default table, to indicate the alternative MCS (e.g., which may be used by base station 105-a to transmit subsequent RARs).

[0140] In some cases, reserved field 220 may include or refer to various fields (e.g., such as TPC command fields, other reserved fields, fields unused in certain DCI formats, etc.), and may be selected based on the amount of information to be conveyed (e.g., whether an indication of the MCS index associated with the alternative MCS is not in the default table, to indicate the scaling factor, the ID of the new MCS table, and / or the MCS index associated with the alternative MCS table). That is, in the case of predefined reserved fields or unused fields, reserved field indication information as described above with reference to reserved fields 220-a and 220-b can be implemented in fields selected based on multiple bits associated with those fields.

[0141] In some examples, the above techniques can also be applied to uplink transmission, where UE 115-a can use reserved fields in uplink transmission to communicate alternative MCS to base station 105-a (e.g., in some cases, UE 115-a can append MCS field 215, reserved field 220, etc. to the random access preamble to indicate alternative MCS associated with Msg2, Msg3, etc.).

[0142] Figure 3 An example of a signaling processing flow 300 supporting alternative MCSs according to various aspects of this disclosure is illustrated. In some examples, processing flow 300 may implement aspects of wireless communication system 100 and wireless communication system 200. Processing flow 300 includes base station 105-b and UE 115-b, which may be as described in reference Figure 1 and Figure 2 Examples of base station 105 and UE 115 are described. Processing flow 300 may illustrate base station 105-b providing UE 115-b with an alternative MCS value for UE 115-b to receive RAR. In the following description of processing flow 300, operations between UE 115-b and base station 105-b may be sent in a different order than the exemplary order shown, or operations performed by UE 115-b and base station 105-b may be performed in a different order or at different times. In some cases, certain operations may be excluded from processing flow 300, or other operations may be added to processing flow 300.

[0143] At 305, UE 115-b can send a random access preamble (e.g., Msg1) to base station 105-b. In some cases (e.g., for random access procedures), UE 115-b can choose RA-RNTI and use RA-RNTI to send the random access preamble.

[0144] At 310, base station 105-b can determine the MCS used for PDSCH transmission (e.g., base station 105-b can determine the MCS used for RAR transmission based on the random access preamble received at 305). Determining the MCS can refer to determining the code rate, modulation scheme, TBS, number of orthogonal frequency division multiplexing (OFDM) symbols indicating the TBS, number of spatial streams, etc., that can be used for PDSCH transmission. For example, at 310, base station 105-b can identify a default set of MCS values ​​and determine that the MCS used for subsequent PDSCH transmission is not included in the default set of MCS values ​​(e.g., base station 105-b can determine that an alternative MCS is not in the default MCS table, and the reserved field of the DCI is used to indicate the alternative MCS).

[0145] At point 315, base station 105-b can identify the type of control information to be sent to UE 115-b in a DCI message. Then, base station 105-b can generate a DCI message and scramble the DCI using RNTI according to the type of control information (e.g., scrambling can be done using SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, etc.). Base station 105-b can then send the scrambled DCI message to UE 115-b. (See reference...) Figure 2 As described, base station 105-b may use at least one bit field (e.g., a reserved field) in the DCI message to provide an indication corresponding to the alternative MCS determined at 310. That is, the DCI message may include an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value (e.g., the alternative MCS) used for PDSCH transmission is included in the default set of MCS values. For example, the DCI message may include (e.g., in the reserved bits) an indication of a scaling factor or an indication of an alternative MCS table, which may indicate that the MCS value used for PDSCH transmission is not included in the default set of MCS values.

[0146] UE 115-b can receive DCI messages and can determine the type of control information included in the DCI message (e.g., control information for a random access message). In one example, UE 115-b can determine the type of control information included in the DCI message based on the RNTI used to decode the DCI message (e.g., RA-RNTI). That is, UE 115-b can determine the type of control information included in the DCI message based on the RNTI used to successfully descramble the CRC bits appended to the DCI message. In some cases, base station 105-b can scramble the DCI using the RA-RNTI that UE 115-b uses to transmit the random access preamble at position 305. In another example, UE 115-b can determine the type of control information included in the DCI message based on the time and / or frequency location of the resources used to transmit the DCI message.

[0147] For example, a corresponding RA-RNTI, addressed by the PDCCH, may exist for each RAR message. The RA-RNTI can be determined based on the time / frequency resources used to transmit the RACH preamble. For instance, all UEs transmitting RACH preambles on the same resources may have the same RA-RNTI and will be addressed by the same PDCCH. Note that after transmitting the RACH preamble, the UE can monitor the set of resources within the configured RAR window to detect RACH responses. This involves searching for the PDCCH with the given RA-RNTI and, upon receiving such a PDCCH, attempting to receive and decode the corresponding RAR message (e.g., decoding the corresponding PDSCH).

[0148] At 320, UE 115-b can determine the MCS value (e.g., an alternative MCS value) used for PDSCH transmission. For example, after UE 115-b identifies the type of control information included in the DCI message, UE 115-b can interpret the bit fields in the DCI message based on that identification. In this example, UE 115-b can determine that the DCI message includes control information for random access messages (e.g., RAR), and UE 115-b can interpret the reserved bit fields of the DCI message based on this determination. Specifically, UE 115-b can determine that one or more reserved bit fields and the MCS field include an indication of an alternative MCS for RAR (e.g., Msg3 transmission). UE 115-b can use these fields to identify the alternative MCS used to receive subsequent PDSCH transmissions from base station 105-b.

[0149] For example, determining the MCS value for PDSCH may include identifying a scaling factor indicated by a reserved bit field in the DCI (e.g., the DCI may include an indication of a scaling factor). The MCS value (e.g., an alternative MCS) can then be determined by multiplying the MCS field of the DCI (e.g., an MCS value in a default set of MCS values) by the indicated scaling factor. In some cases, multiplying the default MCS value by the scaling factor includes identifying the code rate associated with the MCS value in the default set of MCS values ​​and multiplying the identified code rate by the scaling factor. By analogy, multiplying the default MCS value by the scaling factor may include identifying any parameters associated with the MCS (e.g., modulation scheme, TBS, number of REs, etc.) and multiplying the identified MCS parameter by the scaling factor.

[0150] In other cases, determining the MCS value for PDSCH may include identifying an alternative table indicated by the reserved bit field in the DCI. In some cases, the reserved bit field may include an alternative MCS index associated with the alternative MCS table. In other cases, the reserved bit field may indicate the use of an alternative table, and the MCS field of the DCI may indicate an MCS index corresponding to the alternative table (e.g., the alternative MCS can be determined from the alternative table indication in the reserved bit field and the MCS index in the MCS field). In some cases, UE 115-b may determine the MCS value for PDSCH transmission before transmitting the random access preamble (e.g., 320 may occur before 315).

[0151] At 325, base station 105-b can use an alternative MCS to transmit PDSCH transmissions. In this example, the PDSCH transmission can be a RAR message (e.g., it can be transmitted in response to a random access preamble received at 315). Although shown as occurring separately in process flow 300, in some cases, 315 and 325 can occur simultaneously (e.g., DCI and PDSCH can be transmitted simultaneously).

[0152] Figure 4 An example of a signaling processing flow 400 supporting alternative MCSs according to various aspects of this disclosure is illustrated. In some examples, processing flow 400 may implement aspects of wireless communication system 100 and wireless communication system 200. Processing flow 400 includes base station 105-c and UE 115-c, which may be as described in reference Figure 1 and Figure 2 Examples of base station 105 and UE 115 are described. Processing flow 400 may illustrate that base station 105-c provides UE 115-c with an alternative MCS value via a downlink message (e.g., a RAR message) for UE 115-c to send an uplink transmission (e.g., an RRC connection request). In the following description of processing flow 400, operations between UE 115-c and base station 105-c may be sent in a different order than the exemplary order shown, or operations performed by UE 115-c and base station 105-c may be performed in a different order or at different times. In some cases, certain operations may be excluded from processing flow 400, or other operations may be added to processing flow 400.

[0153] At 405, UE 115-c can send a random access preamble (e.g., RACH preamble, Msg1) to base station 105-c.

[0154] At 410, base station 105-c can determine the MCS used for the RRC connection request (e.g., base station 105-c can determine the MCS of Msg3 used for the random access procedure). For example, base station 105-c can determine a default set of MCS values ​​(e.g., a default MCS table). Base station 105-c can also determine whether the MCS value used for the RRC connection request message is included in the default set of MCS values ​​(e.g., to determine whether to use reserved fields of RAR for alternative MCS indications).

[0155] In some cases, base station 105-c can identify MCS values ​​in a default set of values ​​and determine a scaling factor based on those MCS values ​​(e.g., base station 105-c can identify MCS values ​​in a default set of MCS values ​​and determine a scaling factor such that when the scaling factor is multiplied by the identified MCS value, an alternative MCS determined at 410 is given). In other cases, base station 105-c can identify an alternative MCS table that may include the alternative MCS.

[0156] At 415, base station 105-c may send a RAR to UE 115-c. The RAR may include an indication of an alternative MCS (e.g., the alternative MCS may be indicated by the truncated MCS field of Msg2 and one or more reserved fields). The RAR may include an indication of a scaling factor or an indication of an index associated with the substitution table (e.g., via reserved bits and the truncated MCS field of the RAR).

[0157] At 420, UE 115-c can determine the MCS value for the RRC connection request message based at least in part on an indication received at 415 (e.g., in the RAR).

[0158] At 425, UE 115-c can use the MCS determined at 420 to send an RRC connection request (e.g., Msg3). An RRC connection request can also be sent in response to a RAR message received at 415.

[0159] At 430, base station 105-c can send an RRC connection establishment message (e.g., Msg4) to complete / establish an RRC connection with UE115-c.

[0160] In some cases, in addition to some of the operations described in reference processing flow 300, operations performed by UE115-c and base station 105-c can also be performed (e.g., the alternative MCS can be signaled in both DCI and RAR).

[0161] Figure 5A block diagram 500 of a device 505 supporting signaling for an alternative MCS according to various aspects of this disclosure is shown. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a communications manager 515, and a transmitter 520. Device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0162] Receiver 510 can receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and signaling related to alternative MCS). The information can be passed to other components of device 505. Receiver 510 can be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The receiver 510 may utilize a single antenna or a collection of antennas.

[0163] Communication Manager 515 can identify a default set of MCS values ​​and receive a DCI message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. Communication Manager 515 can determine the MCS value used for PDSCH transmission based on the received indication and receive PDSCH transmissions from the base station based on the default set of MCS values ​​and the scaling factor. Communication Manager 515 can also identify a default set of MCS values ​​and receive a RAR message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for RRC connection request messages is included in the default set of MCS values. Communication Manager 515 can determine the MCS value used for RRC connection request messages based on the received indication and send RRC connection request messages to the base station based on the default set of MCS values ​​and the scaling factor. Communication Manager 515 may be an example of various aspects of Communication Manager 810 described herein.

[0164] The communication manager 515 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 515 or its sub-components may be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0165] The communication manager 515 or its subcomponents may be physically located in various locations, including distributed components such that parts of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 515 or its subcomponents may be separate and distinct components. In some examples, the communication manager 515 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0166] Transmitter 520 can transmit signals generated by other components of device 505. In some examples, transmitter 520 may be co-located with receiver 510 in a transceiver module. For example, transmitter 520 may be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The transmitter 520 may utilize a single antenna or a collection of antennas.

[0167] Figure 6 A block diagram 600 of a device 605 supporting signaling for an alternative MCS according to various aspects of this disclosure is shown. Device 605 may be an example of aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a communications manager 615, and a transmitter 650. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] Receiver 610 can receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and signaling related to alternative MCS). The information can be passed to other components of device 605. Receiver 610 can be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The receiver 610 may utilize a single antenna or a collection of antennas.

[0169] Communication manager 615 may be an example of aspects of communication manager 515 as described herein. Communication manager 615 may include MCS table manager 620, DCI manager 625, MCS manager 630, PDSCH manager 635, RAR manager 640, and RRC connection request manager 645. Communication manager 615 may be an example of aspects of communication manager 810 described herein.

[0170] MCS table manager 620 can identify a default set of MCS values. DCI manager 625 can receive a DCI message at the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. MCS manager 630 can determine the MCS value used for PDSCH transmission based on the received indication. PDSCH manager 635 can receive PDSCH transmissions from the base station based on the default set of MCS values ​​and the scaling factor. MCS table manager 620 can identify a default set of MCS values. RAR manager 640 can receive a RAR message at the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for RRC connection request messages is included in the default set of MCS values. MCS manager 630 can determine the MCS value used for RRC connection request messages based on the received indication.

[0171] The RRC Connection Request Manager 645 can send RRC connection request messages to the base station based on the default set of MCS values ​​and scaling factors.

[0172] Transmitter 650 can transmit signals generated by other components of device 605. In some examples, transmitter 650 may be co-located with receiver 610 in a transceiver module. For example, transmitter 650 may be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The transmitter 650 may utilize a single antenna or a collection of antennas.

[0173] Figure 7 A block diagram 700 of a communication manager 705 supporting signaling for alternative MCSs according to various aspects of this disclosure is shown. Communication manager 705 may be an example of aspects of communication manager 515, communication manager 615, or communication manager 810 described herein. Communication manager 705 may include MCS table manager 710, DCI manager 715, MCS manager 720, PDSCH manager 725, random access preamble manager 730, MCS scaling manager 735, alternative MCS table manager 740, RAR manager 745, and RRC connection request manager 750. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0174] The MCS table manager 710 can identify a default set of MCS values. The DCI manager 715 can receive a DCI message at the UE that includes an indication of a scaling factor, wherein the indication of the scaling factor includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. In some cases, the DCI message is scrambled using RA-RNTI, SI-RNTI, P-RNTI, or TC-RNTI. In some cases, the indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values ​​includes at least one bit in the reserved field of the DCI message.

[0175] The MCS manager 720 can determine the MCS value for PDSCH transmission based on received instructions. In some examples, the MCS manager 720 can determine the MCS value for the RRC connection request message based on received instructions. The PDSCH manager 725 can receive PDSCH transmissions from the base station based on a default set of MCS values ​​and a scaling factor. In some cases, PDSCH transmissions include RAR messages. In some cases, the RAR message includes a second message (Msg2) in the random access procedure.

[0176] The RAR manager 745 can receive a RAR message at the UE that includes an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for the RRC connection request message is included in a default set of MCS values. In some cases, the RAR message includes a second message (Msg2) in the random access procedure, and the RRC connection request message includes a third message (Msg3) in the random access procedure. In some cases, the indication of whether the MCS value used for the RRC connection request message is included in the default set of MCS values ​​includes at least one bit in a reserved field of the RAR message. In some cases, the indication that the MCS value used for the RRC connection request message is included in a second set of MCS values ​​includes at least one bit in a reserved field of the RAR message.

[0177] The RRC connection request manager 750 can send an RRC connection request message to the base station based on a default set of MCS values ​​and a scaling factor. In some examples, the RRC connection request manager 750 can send an RRC connection request in response to a RAR message. The random access preamble manager 730 can send a random access preamble to the base station, where a RAR message is sent in response to the random access preamble.

[0178] The MCS scaling manager 735 can receive an indication of a scaling factor. In some examples, the MCS scaling manager 735 can multiply the MCS values ​​in a default set of MCS values ​​with the scaling factor, where the MCS value used for PDSCH transmission is determined based on this multiplication. In some examples, the MCS scaling manager 735 can identify the bitrate associated with the MCS values ​​in the default set of MCS values. In some examples, the MCS scaling manager 735 can multiply the identified bitrate with the scaling factor, where the bitrate associated with the default set of MCS values ​​and the scaling factor is based on this multiplication. In some examples, the MCS scaling manager 735 can receive an indication of the MCS values ​​in the default set of MCS values, where the multiplication is based on the indication of the MCS values ​​in the default set of MCS values. In some examples, the MCS scaling manager 735 can multiply the MCS values ​​in the default set of MCS values ​​with the scaling factor, where the MCS value used for RRC connection request messages is determined based on this multiplication. In some examples, the MCS scaling manager 735 may multiply the identified bitrate by a scaling factor, with the bitrate associated with the determined MCS value for the RRC connection request message based on this multiplication. In some cases, the MCS values ​​in the default set of MCS values ​​correspond to the lowest MCS value in the default set of MCS values. In some cases, the scaling factor indicates whether the MCS value for PDSCH transmission is included in the default set of MCS values. In some cases, the scaling factor indicates whether the MCS value for the RRC connection request message is included in the default set of MCS values.

[0179] The alternative MCS table manager 740 can receive indications of MCS values ​​in a second MCS value set, wherein the MCS value for PDSCH transmission is determined based on the received indications of MCS values ​​in the second MCS value set. In some examples, the alternative MCS table manager 740 can receive an MCS index field. In some examples, the alternative MCS table manager 740 can identify the index associated with the second MCS value set based on the MCS index field and an indication of whether the MCS value for PDSCH transmission is included in a default MCS value set. In some examples, the alternative MCS table manager 740 can receive indications that the MCS value for an RRC connection request message is included in the second MCS value set. In some examples, the alternative MCS table manager 740 can receive indications of MCS values ​​in the second MCS value set, wherein the MCS value for the RRC connection request message is determined based on the received indications of MCS values ​​in the second MCS value set. In some examples, the alternative MCS table manager 740 can identify the index associated with the second MCS value set based on the indication that the MCS value for an RRC connection request message is included in the second MCS value set. In some examples, the alternative MCS table manager 740 can receive MCS index fields.

[0180] In some examples, the alternative MCS table manager 740 can identify the index associated with the second MCS value set based on the MCS index field and an indication that the MCS value for the RRC connection request message is included in the second MCS value set. In some cases, the MCS values ​​in the second MCS value set indicate the code rate, modulation scheme, or a combination thereof. In some cases, the indication of the MCS values ​​in the second MCS value set is an indication that the MCS value for PDSCH transmission is included in the second MCS value set. In some cases, the indication of whether the MCS value for PDSCH transmission is included in the default MCS value set includes an indication that the MCS value for PDSCH transmission is included in the second MCS value set. In some cases, the indication of the MCS values ​​in the second MCS value set includes at least one bit in the reserved field of the DCI message. In some cases, the indication of the MCS values ​​in the second MCS value set is an indication that the MCS value for the RRC connection request message is included in the second MCS value set. In some cases, the indication that the MCS value used for the RRC connection request message is included in the second MCS value set is an indication of whether the MCS value used for the RRC connection request message is included in the default MCS value set.

[0181] Figure 8A diagram of a system 800 including device 805 supporting signaling alternative MCS according to various aspects of this disclosure is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or include its components. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communication, such as a communication manager 810, an I / O controller 815, a transceiver 820, an antenna 825, a memory 830, and a processor 840. These components may communicate electronically via one or more buses (e.g., bus 845).

[0182] The communication manager 810 can identify a default set of MCS values, receive a DCI message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values, and determine the MCS value used for PDSCH transmission based on the received indication. The communication manager 810 can receive PDSCH transmissions from the base station based on the default set of MCS values ​​and the scaling factor. The communication manager 810 can also identify a default set of MCS values ​​and receive a RAR message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for RRC connection request messages is included in the default set of MCS values. The communication manager 810 can determine the MCS value used for RRC connection request messages based on the received indication, and send RRC connection request messages to the base station based on the default set of MCS values ​​and the scaling factor.

[0183] The I / O controller 815 can manage the input and output signals used by the device 805. The I / O controller 815 can also manage peripheral devices not integrated into the device 805. In some cases, the I / O controller 815 can represent the physical connection or port to an external peripheral device. In some cases, the I / O controller 815 can utilize an operating system, such as... Or another known operating system. In other cases, the I / O controller 815 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 815 may be implemented as part of the processor. In some cases, the user may interact with the device 805 via the I / O controller 815 or via hardware components controlled by the I / O controller 815.

[0184] As described above, transceiver 820 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, transceiver 820 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 820 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0185] In some cases, a wireless device may include a single antenna 825. However, in other cases, the device may have more than one antenna 825, which may enable the transmission or reception of multiple wireless signals in parallel.

[0186] Memory 830 may include RAM and ROM. Memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, among others, memory 830 may contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0187] Processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting signaling for alternative MCSs).

[0188] Code 835 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, code 835 may not be directly executable by processor 840, but may enable a computer (e.g., at compile and execution time) to perform the functions described herein.

[0189] Figure 9 A block diagram 900 of a device 905 supporting signaling for an alternative MCS according to various aspects of this disclosure is shown. Device 905 may be an example of various aspects of base station 105 as described herein. Device 905 may include a receiver 910, a communication manager 915, and a transmitter 920. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and signaling related to alternative MCS). The information can be transmitted to other components of device 905. Receiver 910 can be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The receiver 910 may utilize a single antenna or a collection of antennas.

[0191] The communication manager 915 can identify a default set of MCS values ​​and determine whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The communication manager 915 can determine the MCS value used for PDSCH transmission and send a DCI message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The communication manager 915 can send PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor. The communication manager 915 can also identify a default set of MCS values ​​and determine whether the MCS value used for RRC connection request messages is included in the default set of MCS values. The communication manager 915 can determine the MCS value used for RRC connection request messages and send a RAR message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for RRC connection request messages is included in the default set of MCS values. The communication manager 915 can receive RRC connection request messages from the UE based on the default set of MCS values ​​and the scaling factor. Communication manager 915 can be an example of various aspects of communication manager 1210 described herein.

[0192] The communication manager 915 or its sub-components can be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 915 or its sub-components can be performed by a general-purpose processor, DSP, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0193] The communication manager 915 or its subcomponents may be physically located in various locations, including distributed components such that parts of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 915 or its subcomponents may be separate and distinct components. In some examples, the communication manager 915 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0194] Transmitter 920 can transmit signals generated by other components of device 905. In some examples, transmitter 920 may be co-located with receiver 910 in a transceiver module. For example, transmitter 920 may be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The transmitter 920 may utilize a single antenna or a collection of antennas.

[0195] Figure 10 A block diagram 1000 of a device 1005 supporting signaling for an alternative MCS according to various aspects of this disclosure is shown. Device 1005 may be an example of various aspects of device 905 or base station 105 as described herein. Device 1005 may include receiver 1010, communication manager 1015, and transmitter 1050. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0196] Receiver 1010 can receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and signaling related to alternative MCS). The information can be transmitted to other components of device 1005. Receiver 1010 can be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The receiver 1010 may utilize a single antenna or a collection of antennas.

[0197] Communication manager 1015 may be an example of aspects of communication manager 915 as described herein. Communication manager 1015 may include MCS table manager 1020, MCS manager 1025, DCI manager 1030, PDSCH manager 1035, RAR manager 1040, and RRC connection request manager 1045. Communication manager 1015 may be an example of aspects of communication manager 1210 described herein.

[0198] MCS table manager 1020 can identify the default set of MCS values ​​and determine whether the MCS value used for PDSCH transmission is included in the default set of MCS values. MCS manager 1025 can determine the MCS value used for PDSCH transmission. DCI manager 1030 can send a DCI message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. PDSCH manager 1035 can send PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor. MCS table manager 1020 can identify the default set of MCS values ​​and determine whether the MCS value used for RRC connection request messages is included in the default set of MCS values. MCS manager 1025 can determine the MCS value used for RRC connection request messages.

[0199] RAR manager 1040 can send a RAR message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for the RRC connection request message is included in the default MCS value set. RRC connection request manager 1045 can receive the RRC connection request message from the UE based on the default MCS value set and the scaling factor.

[0200] Transmitter 1050 can transmit signals generated by other components of device 1005. In some examples, transmitter 1050 may be co-located with receiver 1010 in a transceiver module. For example, transmitter 1050 may be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The transmitter 1050 may utilize a single antenna or a collection of antennas.

[0201] Figure 11 A block diagram 1100 of a communication manager 1105 supporting signaling for alternative MCSs according to aspects of this disclosure is shown. Communication manager 1105 may be an example of aspects of communication manager 915, communication manager 1015, or communication manager 1210 described herein. Communication manager 1105 may include MCS table manager 1110, MCS manager 1115, DCI manager 1120, PDSCH manager 1125, RAR manager 1130, MCS scaling manager 1135, alternative MCS table manager 1140, and RRC connection request manager 1145. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0202] MCS table manager 1110 can identify the default set of MCS values. In some examples, MCS table manager 1110 can determine whether the MCS value used for PDSCH transmission is included in the default set of MCS values. In some examples, MCS table manager 1110 can identify the default set of MCS values. In some examples, MCS table manager 1110 can determine whether the MCS value used for RRC connection request messages is included in the default set of MCS values. In some examples, MCS table manager 1110 can identify the MCS values ​​in the default set of MCS values. MCS manager 1115 can determine the MCS value used for PDSCH transmission. In some examples, MCS manager 1115 can determine the MCS value used for RRC connection request messages.

[0203] The DCI manager 1120 can send a DCI message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in a default MCS value set. In some cases, the DCI message is scrambled using RA-RNTI, SI-RNTI, P-RNTI, or TC-RNTI. In some cases, the indication of whether the MCS value used for PDSCH transmission is included in the default MCS value set includes at least one bit in a reserved field of the DCI message. In some cases, the indication of the MCS value in a second MCS value set includes at least one bit in a reserved field of the DCI message. In some cases, the indication of whether the MCS value used for the RRC connection request message is included in the default MCS value set includes at least one bit in a reserved field of the DCI message.

[0204] The PDSCH manager 1125 can send PDSCH transmissions to the UE based on a default set of MCS values ​​and a scaling factor. In some cases, the PDSCH transmission includes a RAR message. In some cases, the PDSCH transmission includes a second message (Msg2) during the random access procedure.

[0205] RAR manager 1130 can send a RAR message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for the RRC connection request message is included in the default set of MCS values. In some examples, RAR manager 1130 can receive a random access preamble from the UE, wherein a PDSCH transmission is sent in response to the random access preamble. In some cases, the RAR message includes a second message (Msg2) in the random access procedure; and the RRC connection request message includes a third message (Msg3) in the random access procedure.

[0206] In some cases, the MCS value used for the RRC connection request message is included in a second MCS value set, indicating that at least one bit of the reserved field of the RAR message is included. The RRC connection request manager 1145 can receive the RRC connection request message from the UE based on a default MCS value set and a scaling factor. In some cases, the RRC connection request message responds to the RAR message.

[0207] The MCS scaling manager 1135 can send an indication of a scaling factor, where the scaling factor is based on the determined MCS value used for PDSCH transmission and the MCS values ​​in the default MCS value set. In some examples, the MCS scaling manager 1135 can send an indication of the MCS values ​​in the default MCS value set. In some examples, the MCS scaling manager 1135 can identify the MCS values ​​in the default MCS value set. In some examples, the MCS scaling manager 1135 can send an indication of a scaling factor, where the scaling factor is based on the determined MCS value used for RRC connection request messages and the MCS values ​​in the default MCS value set. In some examples, the MCS scaling manager 1135 can send an indication of the MCS values ​​in the default MCS value set. In some cases, the scaling factor is based on the code rate associated with the determined MCS value used for PDSCH transmission and the code rate associated with the MCS values ​​in the default MCS value set. In some cases, the MCS values ​​in the default MCS value set correspond to the lowest MCS value in the default MCS value set. In some cases, the scaling factor indicates whether the MCS value used for PDSCH transmission is included in the default MCS value set. In some cases, the scaling factor is based on the code rate associated with the determined MCS value used for the RRC connection request message and the code rate associated with the MCS values ​​in the default MCS value set. In some cases, the MCS values ​​in the default MCS value set correspond to the lowest MCS value in the default MCS value set. In some cases, the scaling factor indicates whether the MCS value used for the RRC connection request message is included in the default MCS value set.

[0208] The alternative MCS table manager 1140 can send indications of MCS values ​​in a second MCS value set, where the MCS values ​​in the second MCS value set are based on a default MCS value set and a scaling factor. In some examples, the alternative MCS table manager 1140 can send indications that the MCS values ​​used for RRC connection request messages are included in the second MCS value set. In some examples, the alternative MCS table manager 1140 can send indications of MCS values ​​in a second MCS value set, where the MCS values ​​in the second MCS value set are based on the determined MCS values ​​used for RRC connection request messages.

[0209] In some cases, the MCS values ​​in the second MCS value set indicate the code rate, modulation scheme, or a combination thereof. In some cases, the indication of the MCS values ​​in the second MCS value set includes the MCS index and an indication of whether the MCS value used for PDSCH transmission is included in the second MCS value set. In some cases, the indication of the MCS values ​​in the second MCS value set is an indication that the MCS value used for PDSCH transmission is included in the second MCS value set. In some cases, the indication that the MCS value used for PDSCH transmission is included in the second MCS value set is an indication of whether the MCS value used for PDSCH transmission is included in the default MCS value set. In some cases, the indication that the MCS value used for PDSCH transmission is included in the second MCS value set also indicates the index associated with the second MCS value set. In some cases, the MCS values ​​in the second MCS value set indicate the code rate, modulation scheme, or a combination thereof. In some cases, the indication of the MCS values ​​in the second MCS value set is an indication that the MCS value used for RRC connection request messages is included in the second MCS value set.

[0210] In some cases, the indication of the MCS values ​​in the second MCS value set includes the MCS index and an indication that the MCS value for the RRC connection request message is included in the second MCS value set. In some cases, the indication that the MCS value for the RRC connection request message is included in the second MCS value set is an indication of whether the MCS value for the RRC connection request message is included in the default MCS value set. In some cases, the indication that the MCS value for the RRC connection request message is included in the second MCS value set also indicates the index associated with the second MCS value set.

[0211] Figure 12 A diagram of a system 1200 including device 1205 supporting signaling for alternative MCSs according to various aspects of this disclosure is shown. Device 1205 may be an example of device 905, device 1005, or base station 105 described herein, or include components thereof. Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communication, such components including a communication manager 1210, a network communication manager 1215, a transceiver 1220, an antenna 1225, a memory 1230, a processor 1240, and an inter-station communication manager 1245. These components may communicate electronically via one or more buses (e.g., bus 1250).

[0212] The communication manager 1210 can identify a default set of MCS values, determine whether the MCS value used for PDSCH transmission is included in the default set of MCS values, determine the MCS value used for PDSCH transmission, send a DCI message including an indication of a scaling factor to the UE, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values, and send PDSCH transmissions to the UE based on the default set of MCS values ​​and the scaling factor. The communication manager 1210 can also identify a default set of MCS values, determine whether the MCS value used for RRC connection request messages is included in the default set of MCS values, determine the MCS value used for RRC connection request messages, send a RAR message including an indication of a scaling factor to the UE, wherein the scaling factor indication includes an indication of whether the MCS value used for RRC connection request messages is included in the default set of MCS values, and receive RRC connection request messages from the UE based on the default set of MCS values ​​and the scaling factor.

[0213] The network communication manager 1215 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1215 can manage the transmission of data communication by client devices (such as one or more UEs 115).

[0214] As described above, transceiver 1220 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, transceiver 1220 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1220 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0215] In some cases, a wireless device may include a single antenna 1225. However, in other cases, the device may have more than one antenna 1225, which may be able to transmit or receive multiple wireless transmissions in parallel.

[0216] Memory 1230 may include RAM, ROM, or a combination thereof. Memory 1230 may store computer-readable code 1235 including instructions that, when executed by a processor (e.g., processor 1240), cause the device to perform the various functions described herein. In some cases, among others, memory 1230 may include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0217] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to use a memory controller to operate a memory array. In some cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause the device to perform various functions (e.g., functions or tasks supporting signaling for alternative MCSs).

[0218] Inter-site communication manager 1245 can manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1245 can coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1245 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0219] Code 1235 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1235 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may enable a computer (e.g., at compile and execution time) to perform the functions described herein.

[0220] Figure 13 A flowchart illustrating a signaling method 1300 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1300 can be implemented by, as referred to... Figures 5 to 8 The communication manager described above performs this function. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0221] At step 1305, the UE can recognize the default set of MCS values. The operation at step 1305 can be performed according to the method described herein. In some examples, it can be achieved by referring to... Figures 5 to 8 The MCS table manager is used to perform various aspects of the 1305 operation.

[0222] At 1310, the UE can receive a DCI message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The operation at 1310 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The DCI manager is used to perform various aspects of the operation of 1310.

[0223] At point 1315, the UE can determine the MCS value for PDSCH transmission based on the received indication. The operation at point 1315 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The MCS manager is used to perform various aspects of the operations of 1315.

[0224] At 1320, the UE can receive PDSCH transmissions from the base station based on the default set of MCS values ​​and scaling factors. The operation at 1320 can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 5 to 8 The PDSCH manager is used to perform various aspects of the operation of 1320.

[0225] Figure 14 A flowchart illustrating a signaling method 1400 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1400 can be implemented by, as referred to... Figures 5 to 8 The communication manager described above performs this function. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0226] At step 1405, the UE can recognize the default set of MCS values. The operation at step 1405 can be performed according to the method described herein. In some examples, it can be achieved by referring to... Figures 5 to 8 The MCS table manager is used to perform various aspects of the operation in 1405.

[0227] At 1410, the UE can receive a DCI message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The operation at 1410 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The DCI manager is used to perform various aspects of the operation of 1410.

[0228] At 1420, the UE can multiply the MCS value from the default set of MCS values ​​with a scaling factor, where the MCS value used for PDSCH transmission is determined based on the multiplication. The operation at 1420 can be performed according to the method described herein. In some examples, it can be done as described in the reference... Figures 5 to 8 The MCS scaling manager is used to perform various aspects of the 1420 operation.

[0229] At point 1425, the UE can determine the MCS value for PDSCH transmission based on the received indication. The operation at point 1425 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The MCS manager is used to perform various aspects of the operations in 1425.

[0230] At 1430, the UE can receive PDSCH transmissions from the base station based on the default set of MCS values ​​and scaling factors. The operation at 1430 can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 5 to 8 The PDSCH manager is used to perform various aspects of the operation of 1430.

[0231] Figure 15 A flowchart illustrating a signaling method 1500 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 5 to 8 The communication manager described above performs this function. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0232] At point 1505, the UE can recognize the default set of MCS values. The operation at point 1505 can be performed according to the method described herein. In some examples, it can be achieved by referring to... Figures 5 to 8 The MCS table manager is used to perform various aspects of the 1505 operation.

[0233] At point 1510, the UE can receive a DCI message indicating whether the MCS value used for PDSCH transmission is included in the default MCS value set. The operation at point 1510 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The DCI manager is used to perform various aspects of the operation of 1510.

[0234] At point 1515, the UE can receive an indication of the MCS value in the second MCS value set, wherein the MCS value for PDSCH transmission is determined based on the received indication of the MCS value in the second MCS value set. The operation at point 1515 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The aforementioned alternative MCS table manager performs various aspects of the 1515 operation.

[0235] At 1520, the UE can determine the MCS value for PDSCH transmission based on the received indication. The operation at 1520 can be performed according to the method described herein. In some examples, it can be performed by, as referenced... Figures 5 to 8 The MCS manager is used to perform various aspects of the 1520 operation.

[0236] At point 1525, the UE can receive PDSCH transmissions from the base station based on the determined MCS value used for PDSCH transmission. The operation at point 1525 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The PDSCH manager is used to perform various aspects of the 1525 operation.

[0237] Figure 16 A flowchart illustrating a signaling method 1600 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1600 can be implemented by, as referred to... Figures 5 to 8 The communication manager described above performs this function. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0238] At step 1605, the UE can recognize the default set of MCS values. The operation at step 1605 can be performed according to the method described herein. In some examples, it can be achieved by referring to... Figures 5 to 8 The MCS table manager is used to perform various aspects of the 1605 operation.

[0239] At 1610, the UE can receive a DCI message indicating whether the MCS value used for PDSCH transmission is included in the default MCS value set. The operation at 1610 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The DCI manager is used to perform various aspects of the operation of 1610.

[0240] At point 1615, the UE can receive the MCS index field. The operation at point 1615 can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 5 to 8 The alternative MCS table manager is used to perform various aspects of operation 1615.

[0241] At 1620, the UE can receive an indication of the MCS value in the second MCS value set, wherein the MCS value for PDSCH transmission is determined based on the received indication of the MCS value in the second MCS value set. The operation at 1620 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The aforementioned alternative MCS table manager is used to perform various aspects of the 1620 operations.

[0242] At point 1625, the UE can identify the index associated with the second MCS value set based on the MCS index field and an indication of whether the MCS value used for PDSCH transmission is included in the default MCS value set. The operation at point 1625 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The aforementioned alternative MCS table manager is used to perform various aspects of the 1625 operation.

[0243] At 1630, the UE can determine the MCS value for PDSCH transmission based on the received indication. The operation at 1630 can be performed according to the method described herein. In some examples, it can be performed by, as referenced... Figures 5 to 8 The MCS manager is used to perform various aspects of the 1630's operations.

[0244] At point 1635, the UE can receive PDSCH transmissions from the base station based on the determined MCS value used for PDSCH transmission. The operation at point 1635 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The PDSCH manager is used to perform various aspects of the 1635 operation.

[0245] Figure 17 A flowchart illustrating a signaling method 1700 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE 115 or its components as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 5 to 8 The communication manager described above performs this function. In some examples, the UE can execute a set of instructions to control the UE's functional elements to perform the functions described below. Additionally or alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0246] At 1705, the UE can recognize the default set of MCS values. Operations at 1705 can be performed according to the methods described herein. In some examples, this can be achieved by referring to... Figures 5 to 8 The MCS table manager is used to perform various aspects of the 1705 operation.

[0247] At 1710, the UE can receive a downlink message including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The operation at 1710 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The RAR manager is used to perform various aspects of the operations of 1710.

[0248] At point 1715, the UE can determine the MCS value for uplink transmission based on the received indication. The operation at point 1715 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 5 to 8 The MCS manager is used to perform various aspects of operation 1715.

[0249] At 1720, the UE can send uplink transmissions to the base station based on the default set of MCS values ​​and scaling factors. The operation at 1720 can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 5 to 8 The RRC connection request manager is used to perform various aspects of operation 1720.

[0250] Figure 18 A flowchart illustrating a signaling method 1800 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a base station 105 or its components as described herein. For example, operation of method 1800 can be implemented by, as referred to... Figures 9 to 12 The communication manager described above performs this function. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0251] At point 1805, the base station can recognize the default set of MCS values. Operation at point 1805 can be performed according to the method described in this document. In some examples, this can be achieved by referring to... Figures 9 to 12 The MCS table manager is used to perform various aspects of the 1805 operation.

[0252] At point 1810, the base station can determine the MCS value used for PDSCH transmission. The operation at point 1810 can be performed according to the method described herein. In some examples, it can be done by referring to... Figures 9 to 12The MCS manager is used to perform various aspects of the operation of 1810.

[0253] At step 1815, the base station can determine whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The step 1815 operation can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 9 to 12 The MCS table manager is used to perform various aspects of the operations in 1815.

[0254] At point 1820, the base station can send a DCI message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for PDSCH transmission is included in the default set of MCS values. The operation at point 1820 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 9 to 12 The DCI manager is used to perform various aspects of the 1820's operations.

[0255] In step 1825, the base station can send PDSCH transmissions to the UE based on a default set of MCS values ​​and a scaling factor. Step 1825 operations can be performed according to the method described herein. In some examples, this can be achieved by referring to... Figures 9 to 12 The PDSCH manager is used to perform various aspects of the 1825 operation.

[0256] Figure 19 A flowchart illustrating a signaling method 1900 supporting alternative MCSs according to various aspects of this disclosure is shown. Operation of method 1900 can be implemented by a base station 105 or its components as described herein. For example, operation of method 1900 can be implemented by, as referred to... Figures 9 to 12 The communication manager described above performs this function. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0257] At point 1905, the base station can recognize the default set of MCS values. Operation at point 1905 can be performed according to the method described in this document. In some examples, this can be achieved by referring to... Figures 9 to 12 The MCS table manager is used to perform various aspects of the 1905 operation.

[0258] At point 1910, the base station can determine the MCS value used for uplink transmission. The operation at point 1910 can be performed according to the method described herein. In some examples, it can be done by referring to... Figures 9 to 12 The MCS manager is used to perform various aspects of the 1910 operation.

[0259] At step 1915, the base station can determine whether the MCS value used for uplink transmission is included in the default set of MCS values. The operation at step 1915 can be performed according to the method described herein. In some examples, it can be done by referring to... Figures 9 to 12 The MCS table manager is used to perform various aspects of the operations in 1915.

[0260] At point 1920, the base station can send a downlink message to the UE including an indication of a scaling factor, wherein the scaling factor indication includes an indication of whether the MCS value used for uplink transmission is included in the default set of MCS values. The operation at point 1920 can be performed according to the method described herein. In some examples, it can be performed as described in reference... Figures 9 to 12 The RAR manager is used to perform various aspects of the 1920 operation.

[0261] At 1925, the base station can receive uplink transmissions from the UE based on a default set of MCS values ​​and a scaling factor. The operation at 1925 can be performed according to the method described herein. In some examples, it can be performed as described in the reference... Figures 9 to 12 The RRC connection request manager is used to perform various aspects of the operation in 1925.

[0262] It should be noted that the methods described above describe possible implementations; operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0263] The technologies described herein can be used in various wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and others. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. Versions of IS-2000 may commonly be referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0264] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described here can be used in the systems and radio technologies mentioned above, as well as other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in many descriptions, the technologies described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR applications.

[0265] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 115 with a service subscription to a network provider. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. Depending on various examples, small cells can include picocells, femtocells, and microcells. A picocell, for example, can cover a small geographic area and can allow unrestricted access for UE 115 with a service subscription to a network provider. A femtocell can also cover a small geographic area (e.g., a home) and can provide restricted access to UE 115 associated with a femtocell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 for a user in a home, etc.). An eNB used for a macro cell can be referred to as a macro eNB. An eNB used for a small cell can be referred to as a small cell eNB, pico eNB, femtocell eNB, or home eNB. eNB can support one or more (e.g., two, three, four, etc.) cells, and can also support communication using one or more component carriers.

[0266] One or more wireless communication systems 100 described herein can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately aligned in time. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 can be misaligned in time. The techniques described herein can be used for both synchronous and asynchronous operation.

[0267] The information and signals described herein can be represented using any of a variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout this specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0268] The various illustrative blocks and modules described herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, a processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0269] The functions described herein can be implemented in hardware, software running on a processor, firmware, or any combination thereof. If implemented in software running on a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software running on a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented at different physical locations.

[0270] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store required program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. The disks and optical discs used here include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while optical discs use lasers to copy data optically. Combinations of these are also included within the scope of computer-readable media.

[0271] As used herein, including in the claims, the word "or" used in a list of items (e.g., a list of items beginning with phrases such as "at least one of..." or "one or more of...") indicates an inclusive list, such that a list of at least one of A, B, or C refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0272] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0273] The exemplary configurations described herein, in conjunction with the accompanying drawings, are not representative of all examples that can be implemented or that fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," not "preferred" or "superior to other examples." Detailed descriptions, including specific details, are provided to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0274] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, comprising: Identify the default modulation and coding scheme (MCS) parameter set and the alternative MCS parameter set for the default MCS parameter set; The user equipment (UE) receives a downlink control information (DCI) message scrambled with the radio network temporary identifier (RNTI). Based on the RNTI, identify the type of control information in the DCI message; Based on the control information type in the DCI message, determine an indication to use an alternative MCS set in a field set that includes one or more reserved fields and the MCS fields of the DCI message; Based on the indication of using an alternative MCS set in the field set including one or more reserved fields and DCI messages, identify the MCS parameters from the alternative MCS parameter set for the Physical Downlink Shared Channel (PDSCH) indicated by the RNTI-scrambled DCI message; and The PDSCH transmission is received from the base station based at least in part on the MCS parameters from the alternative MCS parameter set.

2. The method of claim 1, wherein receiving the PDSCH transmission based at least in part on the MCS parameters from the alternative MCS parameter set is based on RNTI for scrambling the DCI message.

3. The method of claim 2, wherein the RNTI used to scramble the DCI message is associated with an MCS parameter indicating a PDSCH transmission not included in the default MCS parameter set.

4. The method of claim 1, wherein the PDSCH transmission includes a Random Access Response (RAR) message.

5. The method of claim 4, further comprising: A random access preamble is sent to the base station, wherein the RAR message responds to the random access preamble.

6. The method of claim 4, wherein the RAR message includes the second message Msg2 during the random access procedure.

7. The method of claim 1, wherein the DCI message is scrambled using a Random Access Radio Network Temporary Identifier (RA-RNTI), a System Information Radio Network Temporary Identifier (SI-RNTI), a Paging Radio Network Temporary Identifier (P-RNTI), or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

8. The method of claim 1, further comprising: The MCS parameters for PDSCH transmission, derived from the alternative MCS parameter set, are determined at least in part by multiplying the MCS parameters of the default MCS parameter set by a scaling factor.

9. The method of claim 8, wherein multiplying the MCS parameters in the default MCS parameter set with the scaling factor comprises: Identify the bitrate associated with the MCS parameter in the default set of MCS parameters; as well as The identified bitrate is multiplied by the scaling factor, wherein the bitrate associated with the determined MCS parameters from the alternative MCS parameter set for the PDSCH transmission is based at least in part on the multiplication.

10. The method of claim 8, further comprising: Receive an indication of the MCS parameters in the default set of MCS parameters, wherein the multiplication is at least in part based on the indication of the MCS parameters in the default set of MCS parameters.

11. The method of claim 8, wherein the MCS parameter in the default MCS parameter set corresponds to the lowest MCS parameter in the default MCS parameter set.

12. A method for wireless communication, comprising: Identify the default modulation and coding scheme (MCS) parameter set and the alternative MCS parameter set for the default MCS parameter set; Determine the MCS parameters for transmission on the Physical Downlink Shared Channel (PDSCH), wherein the MCS parameters are determined to be from the alternative MCS parameter set based on the determination that the MCS parameters are not included in the default MCS parameter set. Based on the determination of the MCS parameters, the type of control information to be transmitted to the user equipment UE in the downlink control information (DCI) message is identified. Based on the control information type, the DCI message scrambled with Radio Network Temporary Identifier (RNTI) is transmitted to the UE, wherein the RNTI-scrambled DCI message indicates, in a field set including one or more reserved fields and an MCS field, the use of the alternative MCS parameter set and the MCS parameters from the alternative MCS parameter set for the PDSCH transmission. as well as The PDSCH transmission is transmitted to the UE based at least in part on the MCS parameters from the alternative MCS parameter set.

13. The method of claim 12, wherein the RNTI used to scramble the DCI message is associated with an MCS parameter indicating a PDSCH transmission not included in the default MCS parameter set.

14. The method of claim 12, wherein the PDSCH transmission includes a Random Access Response (RAR) message, and the method further includes: The UE receives a random access preamble, wherein the RAR message is sent in response to the random access preamble.

15. The method of claim 12, wherein the DCI message is scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a System Information Radio Network Temporary Identifier (SI-RNTI), a Paging Radio Network Temporary Identifier (P-RNTI), or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

16. The method of claim 12, wherein the RNTI-scrambled DCI message indicates a scaling factor, wherein the MCS parameters from the alternative MCS parameter set are at least partially based on the scaling factor and the MCS parameters of the default MCS parameter set, and wherein the RNTI-scrambled DCI message indicates the MCS parameters of the default MCS parameter set.

17. An apparatus for wireless communication, comprising: Memory; and One or more processors are coupled to the memory, said one or more processors being configured to cause the device to: Identify the default modulation and coding scheme (MCS) parameter set and the alternative MCS parameter set for the default MCS parameter set; The device receives a downlink control information (DCI) message scrambled with a radio network temporary identifier (RNTI). Based on the RNTI, identify the type of control information in the DCI message; Based on the control information type in the DCI message, determine an indication to use an alternative MCS set in a field set that includes one or more reserved fields and the MCS fields of the DCI message; Based on the indication of using an alternative MCS set in the field set including one or more reserved fields and DCI messages, identify the MCS parameters from the alternative MCS parameter set for the Physical Downlink Shared Channel (PDSCH) indicated by the RNTI-scrambled DCI message; and The PDSCH transmission is received from the base station based at least in part on the MCS parameters from the alternative MCS parameter set.

18. The apparatus of claim 17, wherein the receiving of PDSCH transmission based at least in part on the MCS parameters from the alternative MCS parameter set is based on RNTI for scrambling DCI messages.

19. The apparatus of claim 18, wherein the RNTI for scrambling DCI messages is associated with an MCS parameter indicating a PDSCH transmission not included in the default MCS parameter set.

20. The apparatus of claim 17, wherein the PDSCH transmission includes a Random Access Response (RAR) message.

21. The apparatus of claim 20, wherein the one or more processors are further configured to cause the apparatus to send a random access preamble to the base station, wherein the RAR message responds to the random access preamble.

22. The apparatus of claim 17, wherein the DCI message is scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a System Information Radio Network Temporary Identifier (SI-RNTI), a Paging Radio Network Temporary Identifier (P-RNTI), or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

23. The apparatus of claim 17, wherein the one or more processors are further configured to cause the apparatus to determine, at least in part, the MCS parameters for PDSCH transmission from the alternative MCS parameter set based on multiplying the MCS parameters of the default MCS parameter set by a scaling factor.

24. The apparatus of claim 23, wherein the one or more processors are configured to: Identify the bitrate associated with the MCS parameters in the default set of MCS parameters; and The identified bitrate is multiplied by the scaling factor, wherein the bitrate associated with the determined MCS parameters from the alternative MCS parameter set for the PDSCH transmission is based at least in part on the multiplication.

25. The apparatus of claim 23, wherein the one or more processors are configured to receive an indication of MCS parameters of the default set of MCS parameters, wherein the multiplication is at least in part based on the indication of MCS parameters of the default set of MCS parameters.

26. An apparatus for wireless communication, comprising: Memory; and One or more processors are coupled to the memory, said one or more processors being configured to cause the device to: Identify the default modulation and coding scheme (MCS) parameter set and the alternative MCS parameter set for the default MCS parameter set; Determine the MCS parameters for transmission on the Physical Downlink Shared Channel (PDSCH), wherein the MCS parameters are determined to be from the alternative MCS parameter set based on the determination that the MCS parameters are not included in the default MCS parameter set. Based on the determination of the MCS parameters, the type of control information to be transmitted to the user equipment UE in the downlink control information (DCI) message is identified. Based on the control information type, the DCI message scrambled with Radio Network Temporary Identifier (RNTI) is transmitted to the UE, wherein the RNTI-scrambled DCI message indicates, in a field set including one or more reserved fields and an MCS field, the use of the alternative MCS parameter set and the MCS parameters from the alternative MCS parameter set for the PDSCH transmission. as well as The PDSCH transmission is transmitted to the UE based at least in part on the MCS parameters from the alternative MCS parameter set.

27. The apparatus of claim 26, wherein the RNTI for scrambling DCI messages is associated with an MCS parameter indicating a PDSCH transmission not included in the default MCS parameter set.

28. The apparatus of claim 26, wherein the PDSCH transmission includes a Random Access Response (RAR) message, wherein the one or more processors are further configured to cause the apparatus to receive a random access preamble from the UE, wherein the RAR message is sent in response to the random access preamble.

29. The apparatus of claim 26, wherein the DCI message is scrambled with a Random Access Radio Network Temporary Identifier (RA-RNTI), a System Information Radio Network Temporary Identifier (SI-RNTI), a Paging Radio Network Temporary Identifier (P-RNTI), or a Temporary Cell Radio Network Temporary Identifier (TC-RNTI).

30. The apparatus of claim 26, wherein the RNTI-scrambled DCI message indicates a scaling factor, wherein the MCS parameters from the alternative MCS parameter set are at least partially based on the scaling factor and the MCS parameters of the default MCS parameter set, and wherein the RNTI-scrambled DCI message indicates the MCS parameters of the default MCS parameter set.

31. An apparatus for wireless communication executed at a user equipment (UE), the apparatus comprising a module for performing the method of any one of claims 1-11.

32. An apparatus for wireless communication performed at a base station (BS), the apparatus comprising a module for performing the method of any one of claims 12-16.

33. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a user equipment (UE) to cause the processor to perform the method of any one of claims 1-11.

34. A computer-readable medium having program code recorded thereon, wherein the program code is executable by one or more processors of a base station BS to cause the processor to perform the method of any one of claims 12-16.

Images