EP3437221A1

EP3437221A1 - Uplink modulation coding scheme and configuration

Info

Publication number: EP3437221A1
Application number: EP16829211.8A
Authority: EP
Inventors: Hong He; Alexei Davydov; Hwan-Joon Kwon; Seunghee Han; Gang Xiong
Original assignee: Intel IP Corp
Current assignee: Apple Inc
Priority date: 2016-03-28
Filing date: 2016-12-29
Publication date: 2019-02-06
Also published as: WO2017171956A1

Abstract

An UpLink (UL) 256-order Quadrature Amplitude Modulation (256QAM) Modulation Coding Scheme (MCS) table, and techniques for configuring communications between a User Equipment (UE) and Evolved NodeB (eNB) using UL 256QAM MCS coding scheme.

Description

UPLINK MODULATION CODING SCHEME AND CONFIGURATION

BACKGROUND

[0001] Wireless systems typically include one or more User Equipment (UE) devices communicatively coupled to one or more Base Stations (BS). The one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) that can be

communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) Long Term Evolved (LTE) network. The UE can be one or more of a smart phone, a tablet computing device, a laptop computer, an internet of things (IOT) device, and/or another type of computing devices that is configured to provide digital communications. As used herein, digital communications can include data and/or voice communications, as well as control information. Communications are sent from the one or more eNBs to the one or more UEs on one or more DownLink (DL) channels, and from the one or more UEs to one or more eNBs on one or more UpLink (UL) channels. The various channels are typically subject to various data rate demands.

[0002] Data rate demands are growing rapidly for both UL and DL transmissions in the wireless system. To support the growing data demand numerous techniques such as carrier aggregation are being developed. Another technique includes the increased use of smaller transmission power, the deployment of small cells and/or the use of more antennas at the eNB. The use of smaller transmission power in combination with smaller cells and/or more antennas typically can be characterized by higher signal-to-noise ratios (SNR) at the receivers in both the DL and UL. However, there remains a continuing need to increase the data rates within a given bandwidth.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

FIG. 1 depicts a wireless system, in accordance with an example;

FIG. 2 illustrates signaling in a wireless system supporting an UpLink (UL) Modulation Coding Scheme (MCS), in accordance with an example; FIG. 3 depicts functionality of an evolved NodeB (eNB ) operable to communicate data using an UL MCS, in accordance with an example;

FIG. 4 depicts functionality of a User Equipment (UE) operable to communicate data using an UL MCS, in accordance with an example; FIG. 5 illustrates a diagram of example components of a UE in accordance with an example;

FIG. 6 illustrates a diagram of an eNB and UE in accordance with an example; and

FIG. 7 illustrates a diagram of example components of a UE in accordance with an example. DETAILED DESCRIPTION

[0004] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

DEFINITIONS

[0005] As used herein, the term "User Equipment (UE)" refers to a computing device capable of wireless digital communication such as a smart phone, a tablet computing device, a laptop computer, a multimedia device such as a television or gaming system, or other type computing device that is configured to provides text, voice, data, or other types of digital communication over wireless communication. The term "User Equipment (UE)" may also be referred to as a "mobile device," "wireless device," of "wireless mobile device."

[0006] As used herein, the term Base Station (BS) refers to a device or configured node of a mobile phone network that communicates wirelessly with UEs. The BS may be a Third-Generation Partnership Project (3GPP) Long Term Evolved (LTE), LTE- Advance, or LTE- Advanced Pro evolved NodeB (eNB), or a similar type of node.

[0007] As used herein, the term "cellular telephone network' or "Long Term Evolved (LTE)" refers to wireless broadband technology developed by the Third- Generation Partnership Project (3GPP).

EXAMPLE EMBODIMENTS

[0008] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0009] Different modulation and coding schemes (MCS) can be used to maximize data transmission rates based on the signal to noise ratio. An MCS includes both a modulation type and a coding scheme. Example modulation types include, but are not limited to, different levels of quadrature amplitude modulation (QAM), such as 8QAM, 16QAM, 64QAM, 128QAM, 256QAM, and so forth. Different types of coding schemes can be used, from efficient coding schemes to robust coding schemes. When there is a higher SNR between a UE and a base station, higher MCS levels (with a higher QAM and/or more efficient coding scheme) can be used to increase the spectral efficiency of the transmission, measured in bits per second per hertz.

[0010] Within each modulation level, multiple different coding schemes can be included. Coding schemes can be used to recover from transmission errors. More robust coding schemes can recover from higher bit error rates, while reducing the overall transmission throughput. Conversely, more efficient coding schemes can allow for higher transmission throughput, while reducing the ability to recover from transmission errors. With relatively high SNRs, it is possible to use both high modulation levels (i.e. 16QAM, 64QAM) and efficient coding schemes. As the SNR decreases, more robust coding schemes can be used, until the SNR decreases to a point where a lower modulation level (i.e. QAM, BPSK) can be used to increase the spectral efficiency. A table can be used to identify specific coding schemes and modulation levels that can be used for a specific SNR range. The table can also include other information, as discussed in the proceeding paragraphs. [0011] UL transmissions typically have a lower SNR than DL transmissions, since transmission power from the UE is limited. However, in certain instances a UE may only transmit a short distance to a base station in a relatively noise free environment. For example, when a low power base station is located in a same room or same building as a UE, it can be possible for the UE to transmit an UL signal with a relatively high SNR. The use of an increased MCS can take advantage of the relatively high SNR to increase the spectral efficiency of the UL transmission, thereby enabling higher UL transmission rates by the UE. In addition, the increased spectral efficiency may reduce the amount of power used to transmit each bit.

[0012] In one aspect, techniques for communicating data between a User

Equipment and an eNB can include an UpLink (UL) Modulation Coding Scheme (MCS) table covering the SNR operational range of a 256-order Quadrature Amplitude

Modulation (256QAM) capability to improve the UL spectrum efficiency.

[0013] In one aspect, signaling methods can support independent DL and UL table configurations per Control Channel (CC), or per CC per UL subframe set, or per antenna ports, in accordance with flexible 256QAM capability reporting of a UE. In one aspect, Level one (LI) signaling schemes can support fallback operation to ensure a robust connection between the eNB and the UE. In one aspect, subframe-set-dependent MCS table configurations can improve the throughput performance, which may be applied when more than one UL subframe set is configured for a given UE. In one aspect, MCS-table specific resources can be determined for Uplink Control Information (UCI) on Physical Uplink Shared Channels (PUSCH). In one aspect, MCS-table-specific power control offset parameters can be provided for PUSCH transmissions.

[0014] FIG. 1 depicts a wireless system, in accordance with an example. In one aspect, the wireless system 100 includes one or more Base Stations (BS) 110 and one or more User Equipment (UE) devices 120 that can be communicatively coupled by a wireless communication protocol. In one instance, the one or more BSs may be Long Term Evolved (LTE) evolved NodeBs (eNB) that can be communicatively coupled to one or more UEs by a Third-Generation Partnership Project (3GPP) Long Term Evolved (LTE) network. In one instance, the UE can be one or more of a smart phone, a tablet computing device, a laptop computer, an internet of things (IOT) device, and/or another type of computing devices that is configured to provide digital communications. As used herein, digital communications can include data and/or voice communications, as well as control information. The communications can be exchanged between one or more eNB and one or more UE using one or more Modulation Coding Schemes (MCS).

[0015] FIG. 2 illustrates signaling in a wireless system supporting an UpLink (UL) Modulation Coding Scheme (MCS), in accordance with an example. In one aspect, UE capability reporting can provide for support of 256-order modulation for PUSCH transmission and configuration of an applicable UL MCS table.

[0016] In one aspect, the eNB 205 can encode a capability inquiry message 215 for transmission to a User Equipment (UE) 210. A Radio Access Technology (RAT) type for the capability inquiry message can be set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN). In one aspect, the UE 210 can decode the capability inquiry message 215 received from the eNB 205. The UE 210 can determine the RAT type from the capability inquiry message 215.

[0017] In one aspect, the UE 210 can encode a UE capability information message 220 including an indicator of MCS capability when the RAT type is set to E- UTRAN. In one aspect, the eNB 205 can decode the UE capability information message 220 received from the UE 210. The UE capability information message 220 can include a legacy Quadrature Amplitude Modulation (QAM) or a 256-order Quadrature Amplitude Modulation (256QAM) coding scheme indicator.

[0018] In one instance, the capability of supporting 256QAM, for each supported band or on a per band per band combination, can be reported independently for DL and UL using two separate Information Elements (IE) 225. In one example, support may be provided in the following exemplary code:

SupportedBandEUTRA-vl4xx : := SEQUENCE {

dl-256QAM-rl2 ENUMERATED {supported}

OPTIONAL,

ul-256QAM-rl4 ENUMERATED {supported}

OPTIONAL

}

Wherein, dl-256QAM indicates whether the UE supports 256QAM in DL on the band, and ul-256QAM indicates whether the UE supports 256QAM in UL on the band. [0019] In one aspect, the eNB 210 can encode a first signaling message 230 including UL MCS table information for transmission to the UE 210 in response to a 256QAM coding scheme indicator. In one instance, the first signaling message 230 may include an MCS table configuration message. In one aspect, the UE 210 can decode the first signaling message 230 including the UL MCS information received from the eNB 205. In one aspect, the UE 210 can determine an UL MCS table for a 256QAM coding scheme 235 from a plurality of MCS tables based on the UL MCS information.

[0020] In one instance, the E-UTRAN eNB may independently configure the UE with one DL MCS table and/or one UL MCS table 240 selected from a plurality of MCS tables to use for DL reception and UL transmission respectively through one RRC message in accordance with 256QAM capability of the UE obtained in the UE capability information message. The 256QAM MCS table can be independently configured in DL and UL for a given UE. It is to be noted that when two UL subframe sets are configured by a higher layer, the UL 256QAM MCS table can be configured for both two subframe sets, or applied to one subframe set as illustrated in the following exemplary code:

altULMCS-Table-rl4 ENUMERATED {

allSubframes, UL-SubframeSetl,

UL-SubframeSet2, sparel } OPTIONAL

Need OP

Wherein altULMCS-Table indicates the applicability of the alternative UL MCS table (i.e. UL 256QAM MCS table) for the concerned cell. The value allSubframes indicates the alternative UL MCS table applies to the subframes, if configured, a UL-SubframeSetl indicates the alternative UL MCS table applies to UL subframe setl, and value UL- SubframeSet2 indicated the alternative UL MCS table applies to UL subframe set2. If this field is not present, the UE shall use the legacy UL MCS table for all subframes, if configured.

[0021] In another aspect, one MCS table can be configured individually for each serving cell, and/or per UL subframe set or per UL power control loop, and/or per antenna port or MIMO layer. The latter option is motivated by the fact that the UE may implement different RF power amplifiers with different maximum transmission power for different antenna. [0022] In another aspect, the DL MCS table and the UL MCS table can be jointly configured by one IE assuming a similar SINR status occurs at a receiver side for both DL and UL. As an example, the legacy DL/UL MCS table supporting 6-orders of modulation can be configured for a serving cell if a corresponding IE was set to a predefined value or not present. In one instance, if a higher layer parameter such as altCQI-Table-rl2 is configured, the UE assumes the 256QAM MCS table can be applied in both DL and UL for PDSCH and PUSCH scheduled by DCI format with CRC scrambled by C-RNTI. Otherwise, the UE can assume the legacy MCS tables are used for data transmission and reception.

[0023] In another aspect, the UE 210 can receive a DCI format (e.g., DCI format

0 or 4) for PUSCH transmission 245. The UE 210 may determine the actual UL MCS table based on an MCS table configuration and the corresponding information conveyed in the DCI format for the PUSCH transmission.

[0024] In another aspect, several different schemes can be utilized to indicate a corresponding MCS table used for PUSCH transmission by means of the DCI format (e.g., DCI format 0 or 4). In one instance, one UL MCS table from a plurality of MCS tables may be configured by higher layers semi-statically. In another instance, an UL MCS table identifier may be included in a DCI format used for the scheduling of PUSCH (i.e. DCI format 0 or 4) to identify one MCS table from a plurality of MCS tables to determine modulation and coding to be utilized for PUSCH transmission. One bit in the DCI format may indicate the UL MCS table. In one example, the value "0" is used to indicate the legacy UL MCS table, and the value "1" is used to indicate the UL 256QAM MCS table.

[0025] In another instance, the legacy UL MCS table can be selected for PUSCH if the associated DCI format 0 or 4 is transmitted in Common Search Space (CSS) and the UL 256QAM MCS table can be used for PUSCH if the associated DCI format 0 or 4 is transmitted in UE-specific Search Space (USS). Alternatively or additionally, a UE may determine the selected UL MCS table based on the physical channels used to convey the DCI format 0 or 4. For example, the UE can use the legacy UL MCS table if it is conveyed in the first EPDCCH resource set. The UE can use the UL 256QAM MCS table if the corresponding DCI format is conveyed in the second EPDCCH resource set. A combination of these alternative schemes may also be utilized. In another instance, as illustrated in Table 1, the UL MCS table can be indicated by the sequence used to scramble the CRC bits of UL DCI formats.

Table 1

The CRC bits of DCI formats, used for UL grant, are scrambled with a selected sequence according to the intended MCS table.

[0026] In another instance, the UL MCS table can be indicated by different C- RNTI values. The legacy UL MCS table can be used if the CRC bits of a DCI format are scrambled with a first C-RNTI value and the UL 256QAM MCS table can used if the CRC bits of a DCI format are scrambled with a second C-RNTI value. In another instance, the UL MCS table can be implicitly determined by the aggregation level of a corresponding DCI format used for PUSCH scheduling. For example, the aggregation levels (ALs) in a US S may be divided into two sets, wherein the first set of ALs comprises of AL-1 and AL-2 and the second set of ALs comprise of AL-4 and AL-8. The UE can use the UL 256QAM MCS table if the first set (i.e. AL-1 or AL-2) is used for DCI format transmission. The legacy UL MCS table can be selected if the second set is used for DCI format transmission.

[0027] In another instance, the UL MCS table may be implicitly indicated based on which DCI format is used for the corresponding PUSCH scheduling. For example, a UE can assume the legacy UL MCS table is selected for PUSCH transmission if it is scheduled by DCI format 0 regardless of the configured MCS table. The UE can assume the UL 256QAM MCS table is used for PUSCH transmission if UL 256QAM MCS table is configured for this UE and the PUSCH is scheduled by DCI format 4. In another instance, when more than one UL subframe set is configured for a given UE, the UL MCS table can be indicated by which UL subframe set is scheduled for PUSCH transmission. For example, if the scheduled PUSCH is transmitted on the first UL subframe set, the legacy UL MCS table can be used; otherwise, the UL 256QAM MCS table is used for PUSCH transmission. [0028] In one aspect, the UE can encode data for transmission on the PUSCH using the UL 256QAM MCS table 250. In one aspect, the eNB can decode the PUSCH messages received from the UE using the UL MCS table for the 256QAM coding scheme.

[0029] In one aspect, resource determination can be provided for Uplink Control

Information (UCI). The UCI can include at least HARQ-ACK (hybrid automatic request repeat acknowledgement), CQI (Channel quality indicator), RI (Rank Indicator), and BI (Beam selection Indicator). When the UE transmits UCI on PUSCH, the number of coded symbols or REs used for communicating the UCI on the PUSCH can be determined based on the value of a corresponding UCI offset parameter that is associated with the identified MCS table. In one instance, two sets of UCI offset parameters may be configured by higher layers for the number of REs, determined in case of UCI on PUSCH, wherein the first set of UCI offset parameters are associated with the legacy UL MCS table and the second set of UCI offset parameters are linked to the UL 256QAM MCS table or at least the 256QAM entries in the UL 256QAM MCS table. A first set of UCI offset parameters can include: · ^A second set of UCI offset parameters c toff set.i,■

[0030] In one example, two sets of UCI offset parameters may be collectively configured by a UE, for the determined number of UCI REs, when two UL subframe sets are configured for a given UE. Two UL subframe sets may be configured, for example in elMTA (Enhanced Interference Mitigation and Traffic Adaptation) or ICIC (Inter-cell interference coordination), and the UE is likely to experience drastically different channel conditions. The association between UCI offset parameter and the corresponding UL subframe set can be implicitly determined. A first set of UCI offset parameters associated with the legacy UL MCS table can be used for determining the number of UCI REs on the first UL subframe set due to typically stronger cross-link interference than the second subframe set. A second set of UCI offset parameters associated with the UL 256QAM MCS table can be used for deriving the number of UCI REs for PUSCH on the second subframe set. In another example, two sets of UCI offset parameters can be configured for each UL subframe set. The UCI offset parameter for each UL subframe in a UL subframe set can be determined based on the identified MCS table. [0031] In another aspect, transport format (TF) compensator parameter A_TF can be derived using two different fixed MCS-specific K_s values in accordance with the corresponding UL MCS table used for PUSCH transmission. In LTE, PUSCH transmission power can be determined as follows: (0 = ( ) + /( )}

In above equation, one element A_TF(. = 10log₁₀ 2^{MPR Ks} - i)/?^pt/5Cii _can be determined based on spectrum efficiency factor MPR and a compensator factor K_s.

[0032] In another aspect, two parameters K_{s l}, K_{s 2} can be used in association with two UL MCS tables (i.e. legacy and 256QAM MCS table). For example, the K_{s l} (K_{s l} = 1.25) may be associated with the legacy UL MCS table and the K_{s 2} may be associated with the new UL 256QAM MCS table or at least the 256QAM entries in the UL

256QAM MCS table. The UE can determine the MCS specific parameter K_s to adjust the transmission power of a scheduled PUSCH in subframe n based on the corresponding parameter K_{s l} or K_{s 2} in accordance with the identified UL MCS table. [0033] FIG. 3 depicts functionality of an evolved NodeB (eNB ) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), in accordance with an example. Communicating data using the UL MCS including a 256- order Quadrature Amplitude Modulation (256QAM) capability can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the priority based resource allocation.

[0034] In one aspect, the eNB can encode a capability inquiry message for transmission to a User Equipment (UE) 310. The Radio Access Technology (RAT) type for the capability inquiry message can be set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN).

[0035] In one aspect, the eNB can decode a UE capability information message received from the UE 320. In one instance the UE capability information message can include an UL and a DL coding scheme indicator. The UE capability information message can include a legacy Quadrature Amplitude Modulation (QAM) or a 256QAM coding scheme indicator for UL transmissions. The legacy QAM may include one or more of a 64QAM, a 16QAM and a Quadrature Phase Shift Keying (QPSK) coding scheme. In one instance, E-UTRAN can support three different MCSs for PUSCH transmission using an MCS table, including QPSK, 16QAM and 64QAM. The UE capability information message can include a DownLink (DL) 256QAM capability in a first Information Element (IE) along with a UL 256QAM capability in a second IE for a plurality of supported bands, or for a per band per band combination. If the UE capability message includes a legacy QAM coding scheme indicator, UL MCS table information does not need to be transmitted to the UE. In addition, a DCI format on a first set of PDCCH candidates to schedule 256QAM does not need to be transmitted to the UE.

[0036] In one aspect, the eNB can encode a first signaling message including UL

MCS table information for transmission to the UE in response to a 256QAM coding scheme indicator 330. In one instance, the first signaling message may include an MCS table configuration message. The first signaling message can be encoded as an UL dedicated Radio Resource Control (RRC) message. In one aspect, the eNB can encode a Downlink Control Information (DCI) format on a first set of Physical Downlink Control Channel (PDCCH) candidates to schedule 256QAM for Physical Shared Channel (PUSCH) transmission to the UE 340. The first set of PDCCH candidates can be in UE- specific search space at least determined by a Cell-Radio Network Temporary Identifier (C-RNTI) assigned for the UE and slot number where the DCI format is monitored.

[0037] The UL MCS table for the 256QAM coding scheme may be the same size as the UL MCS table for a legacy QAM coding scheme, such as for instance the UL 64QAM MCS table. The UL 256QAM MCS table may include a plurality of MCS entries reserved for indicating Redundancy Version (RV) of a Physical Uplink Shared Channel (PUSCH) non-adaptive retransmission. In one instance, for example, the UL 256QAM MCS table may include three (3) entries reserved for RV of PUSCH non- adaptive retransmission. The UL 256QAM MCS table may include a full Signal-to-Noise Ratio (SNR) operation range of QPSK, 16QAM, 64QAM and 256QAM. The UL MCS table for the 256QAM coding scheme can include a down-sampled low Signal-to- Interference-Noise Ratio (SINR) QPSK region of the legacy QAM coding scheme portion of the UL MCS table that has an even SINR space and keeps one or more QPSK entries. One or more duplicated MCS indices with duplicate Transport Block Size (TBS) indices can be removed so that the duplicated MCS indices are not included in the legacy UL MCS table portion. One or more new MCS entries with equal spacing can fill an SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes.

[0038] The first signaling message including one DL MCS table information and one UL MCS table information can be selected from a plurality of DL MCS tables and UL MCS tables through one Radio Resource Control (RRC) message in accordance with the 256QAM coding scheme indicator. The UL 256QAM MCS table can be configured for either one or two subframe sets, when two subframe sets are configured for the UE. The first signaling can be encoded in a Downlink Control Information (DCI) format including the UL MCS table information. The DCI format includes an UL MCS table identification to identify one MCS table from a plurality of MCS tables to determine modulation and coding for the PUSCH message.

[0039] In one aspect, the eNB can decode a PUSCH message received from the UE using the UL MCS table for the 256QAM coding scheme 350. In one instance, the UL 256 AM MCS table may be as illustrated in Table 2:

21 8 26 0

22 8 27 0

23 8 28 0

24 8 29 0

25 8 30 0

26 8 31 0

27 8 32 0

28 8 33 0

29 1

30 Reserved 2

31 3

Table 2

The exemplary table includes the MCS index (IMCS), the Modulation Order (Qm), the Transport Block Size (ITBS), and Redundancy Version (rvidx). The UL MCS table may be the same size as a legacy UL MCS table to remain the same number of MCS bits in the DCI format and avoid extra DL control overhead. Three MCS entries may be reserved for Redundancy Version (RV) of the PUSCH non-adaptive retransmission.

[0040] The exemplary MCS table can cover a full Signal-to-Noise Ratio (SNR) operational range of QPSK, 16QAM, 64QAM and 256QAM to eliminate the need for UL MCS table reconfiguration in the case of short term Signal-Interference-to-Noise Ratio (SINR) fluctuation due to transients, such as sudden traffic load fluctuations in interference cells. The UL 256QAM MCS table can be enabled for a UE if its channel condition is favorable. Hence to create enough spare space to incorporate 256QAM entries, the low SINR QPSK region in the legacy UL MCS table may be evenly down- sampled while keeping some QPSK entries for robust operation and fine Transport Block Size (TBS).

[0041] In the exemplary MCS table some duplicated MCS indices with duplicate TBS indices in the legacy portion of the UL MCS table can be removed without impacting the TBS resolution. Several new MCS entries can be added with equal spacing to fill the SNR gap between maximum spectrum efficiency target of 64QAM and

256QAM. It is noted that this table with eight entries for 256QAM (e.g., Q_m=8) is shown for purpose of explanation, and is not intended to be in any way limiting. In principle, a lower order modulation with higher coding rate can offer better performance than a higher order modulation with lower code rates by the single carrier-frequency division multiple access (SC-FDMA) signal. Correspondingly, the number of 256QAM entries in the UL 256QAM MCS table may be less than in a DL 256QAM MCS table (i.e. eight) to optimize Single Carrier Frequency Division Multiple Access (SC-FDMA) link performance. In another instance, the UL 256QAM MCS table may be designed to share a set of common MCS entries with a legacy UL MCS table. In one instance, the set of entries shared between the legacy UL MCS table the UL 256QAM MCS table may not include consecutive indices.

[0042] FIG. 4 depicts functionality of a User Equipment (UE) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), in accordance with an example. Communicating data using the UL MCS including a 256- order Quadrature Amplitude Modulation (256QAM) capability can be implemented by one or more processors and memory, wherein the memory stores one or more sets of instructions that when executed by the one or more processors perform one or more functionalities including the priority based resource allocation.

[0043] In one aspect, the UE can decode a capability inquiry message received from an evolved NodeB (eNB) 410. In one aspect, the UE can determine a Radio Access Technology (RAT) type from the capability inquiry message 420.

[0044] In one aspect, the UE can encode a UE capability information message including an indicator of an UL 256-order Quadrature Amplitude Modulation (256QAM) capability and another indicator of a DL 256QAM capability when the RAT type is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 430. The UE capability information message encoded by the UE can include a DownLink (DL) 256QAM capability in a first Information Element (IE) and a UL 256QAM capability in a second IE for a plurality of supported bands, or for a per band per band combination.

[0045] In one aspect, the UE can decode a first signaling message including an

UL modulation coding scheme (MCS) information received from the eNB 440. The first signaling message may include an MCS table configuration for UL, and optionally DL transmissions. The first signaling can be an UL dedicated Radio Resource Control (RRC) message. The first signaling can include one DL MCS table information and one UL MCS table information selected through one RRC message. [0046] In one aspect, the UE can determine an UL MCS table for a 256QAM coding scheme from a plurality of MCS tables based on the UL MCS information 450. In one aspect, the UE can determine a modulation order and a Transport Block Size (TBS) using a legacy QAM coding scheme if the DCI format is transmitted in a Common Search Space (CSS). The plurality of MCS tables can include a Quadrature Phase Shift Keying (QPSK) MCS table, a 16QAM MCS table, a 64QAM MCS table, and the 256QAM MCS table. In one instance, the plurality of MCS tables can include an UL MCS table that supports up to a 64QAM coding scheme and an UL MCS table that supports up to a 256QAM coding scheme. The number of 256QAM entries in the UL 256QAM MCS table can be less than in a DownLink (DL) 256QAM MCS table. In one instance, the UL 256QAM may be as illustrated in Table 2, as described above.

[0047] The UL MCS table that supports up to the 256QAM coding scheme may include a table size the same as a table size of the UL MCS table that supports up to a 64 QAM coding scheme (i.e. a same number of entries). The UL 256QAM MCS table may include a plurality of entries reserved to indicate a redundancy version (RV) of a Physical Uplink Shared Channel (PUSCH) non-adaptive retransmission. In one instance, the table may include three entries reserved to indicate the RV of the PUSCH non-adaptive retransmission. The UL 256QAM MCS table may include a Signal-to-Noise Ratio (SNR) operational range of QPSK, 16QAM, 64QAM and 256QAM. The UL 256QAM MCS table may include a down-sampled low Signal Interference Noise Ratio (SINR) QPSK region in a portion of the UL MCS table associated with up to 64QAM support with an even SINR space that keeps one or more QPSK entries. The UL 256QAM MCS table may include one or more duplicated MCS indices, with duplicate TBS indices, that may be removed from a legacy portion of the UL MCS table. The UL 256QAM MCS table may include a plurality of new MCS entries with equal spacing to fill the SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes.

[0048] The UL 256QAM MCS table can be configured for either one or two subframe sets, when two subframe sets are configured for the UE. The UL MCS table and the DL MCS table can be configured by one Information Element (IE). The first signaling can be decoded in a Downlink Control Information (DCI) format including the UL MCS table information. In one instance, an UL MCS identifier can be determined in a Downlink Control Information (DCI) format used for scheduling Physical Uplink Shared Channel (PUSCH) transmissions. The UL MCS table can be selected from the plurality of MCS tables using the UL MCS identifier.

[0049] In another instance, a search space where a DCI format of 0 or 4 is transmitted can be detected. The UL 64QAM MCS table can be selected if the associated DCI format 0 or 4 is transmitted in Common Search space (CSS). The UL 256QAM MCS table can be selected if the associated DCI format 0 or 4 is transmitted in UE- specific Search Space (USS).

[0050] In another instance, an enhanced Physical Downlink Control Channel (ePDCCH) set index can be determined. The UL 64QAM MCS table can be selected if the DCI format of 0 or 4 is transmitted in a first ePDCCH resource set. The UL 256QAM MCS table can be selected if the DCI format of 0 or 4 is transmitted in a second ePDCCH resource set.

[0051] In another instance, the DCI format can be determined. The UL 64QAM MCS table can be selected if the DCI format of 0 is determined. The UL 256QAM MCS table can be selected if the DCI format of 4 is determined.

[0052] In another instance, an MCS table selection mark sequence used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format can be determined. The UL 64QAM MCS table can be selected if a first MCS table selection mark sequence is determined. The UL 256QAM MCS table can be selected if a second MCS table selection mark sequence is determined.

[0053] In another instance, a Cell Radio Network Topology Identifier (C-RNTI) value used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format can be determined. The UL 64QAM MCS table can be selected if a first C-RNTI value is determined. The UL 256QAM MCS table can be selected if a second C-RNTI value is determined.

[0054] In another instance, an aggregation level used to transmit an UL DCI format can be determined. The UL 64QAM MCS table can be selected if one of a first set of aggregation levels is determined. The UL 256QAM MCS table can be selected if one of a second set of aggregation levels is determined.

[0055] While examples have illustrated that the 64QAM MCS table can be associated with first values (i.e. a table selection mark sequence, a C-RNTI value, a set of aggregation levels, etc.), and the 256QAM MCS table can be associated with second values, this is not intended to be limiting. The 64QAM MCS table can also be associated with second values, while the 256QAM MCS table can be associated with first values.

[0056] In one aspect, the UE can decode two sets of Uplink Control Information (UCI) offset parameters associated with different UL MCS tables. A number of coded symbols or Resource Elements (REs), for UCIs on PUSCH, can be determined based on a value of a corresponding UCI offset parameter that is associated with the determined UL 256QAM MCS table. A first set of UCI offset parameters can be associated with the UL 64QAM MCS table. A second set of UCI offset parameters can be linked to the UL 256QAM MCS table or 256QAM entries in the UL 256QAM MCS table. The UCI can include at least hybrid automatic request repeat acknowledgment (HARQ-ACK), Channel Quality Indicator (CQI), Rank Indicator (RI), and Beam selection Indicator (BI).

[0057] In one aspect, the UE can encode data for transmission on a PUSCH using the UL MCS table for the 256QAM coding scheme (also referred to herein as UL 256QAM MCS table) if an associated DCI format is transmitted in a UE-Specific Search Space (USS) in accordance with the first signaling method 460. In one instance, the PUSCH message can be encoded using different power compensator factor values associated with the UL 256QAM MCS table. A first value can be associated with the 64QAM coding scheme portion of the UL MCS table. A second value can be associated with the 256QAM coding scheme portion of the UL MCS table.

[0058] FIG. 5 illustrates a diagram of example components of a UE device in accordance with an example. In some aspects, the UE device 500 can include application circuitry 502, baseband circuitry 504, Radio Frequency (RF) circuitry 506, front-end module (FEM) circuitry 508 and one or more antennas 510, coupled together at least as shown. It is to be appreciate that the eNB can also include similar example components that function similar to the components of the UE device described below.

[0059] The application circuitry 502 can include one or more application processors. For example, the application circuitry 502 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include memory /storage and can be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system.

[0060] The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with and/or can include a storage medium 512, and can be configured to execute instructions stored in the storage medium 512 to enable various applications and/or operating systems to run on the system.

[0061] The baseband circuitry 504 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 504 can include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 506 and to generate baseband signals for a transmit signal path of the RF circuitry 506. Baseband processing circuitry 504 can interface with the application circuitry 502 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 506. For example, in some aspects, the baseband circuitry 504 can include a second generation (2G) baseband processor 504a, third generation (3G) baseband processor 504b, fourth generation (4G) baseband processor 504c, WiFi baseband processor 504d and/or other baseband processor(s) 504e for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 504 (e.g., one or more of baseband processors 504a-d) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 506. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some aspects, modulation/demodulation circuitry of the baseband circuitry 504 can include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some aspects, encoding/decoding circuitry of the baseband circuitry 504 can include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Aspects of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other aspects.

[0062] In some aspects, the baseband circuitry 504 can include elements of a protocol stack such as, for example, elements of an Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 504f of the baseband circuitry 504 can be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some aspects, the baseband circuitry can include one or more audio digital signal processor(s) (DSP) 504g. The audio DSP(s) 504g can be include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other aspects.

Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some aspects. In some aspects, some or all of the constituent components of the baseband circuitry 504 and the application circuitry 502 can be implemented together such as, for example, on a system on a chip (SOC).

[0063] In some aspects, the baseband circuitry 504 can provide for

communication compatible with one or more radio technologies. For example, in some aspects, the baseband circuitry 504 can support communication with an EUTRAN and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Aspects in which the baseband circuitry 504 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0064] RF circuitry 506 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various aspects, the RF circuitry 506 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 506 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 508 and provide baseband signals to the baseband circuitry 504. RF circuitry 506 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 504 and provide RF output signals to the FEM circuitry 508 for transmission.

[0065] In some aspects, the RF circuitry 506 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 506 can include mixer circuitry 506a, amplifier circuitry 506b and filter circuitry 506c. The transmit signal path of the RF circuitry 506 can include filter circuitry 506c and mixer circuitry 506a. RF circuitry 506 can also include synthesizer circuitry 506d for synthesizing a frequency for use by the mixer circuitry 506a of the receive signal path and the transmit signal path. In some aspects, the mixer circuitry 506a of the receive signal path can be configured to down-convert RF signals received from the FEM circuitry 508 based on the synthesized frequency provided by synthesizer circuitry 506d. The amplifier circuitry 506b can be configured to amplify the down-converted signals and the filter circuitry 506c can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitry 504 for further processing. In some aspects, the output baseband signals can be zero-frequency baseband signals, although the output baseband signals do not have to be zero-frequency baseband signals. In some aspects, mixer circuitry 506a of the receive signal path can comprise passive mixers, although the scope of the aspects is not limited in this respect.

[0066] In some aspects, the mixer circuitry 506a of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 506d to generate RF output signals for the FEM circuitry 508. The baseband signals can be provided by the baseband circuitry 504 and can be filtered by filter circuitry 506c. The filter circuitry 506c can include a low-pass filter (LPF), although the scope of the aspects is not limited in this respect.

[0067] In some aspects, the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and/or up conversion respectively. In some aspects, the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some aspects, the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a can be arranged for direct down conversion and/or direct up conversion, respectively. In some aspects, the mixer circuitry 506a of the receive signal path and the mixer circuitry 506a of the transmit signal path can be configured for super-heterodyne operation.

[0068] In some aspects, the output baseband signals and the input baseband signals can be analog baseband signals, although the scope of the aspects is not limited in this respect. In some alternate aspects, the output baseband signals and the input baseband signals can be digital baseband signals. In these alternate aspects, the RF circuitry 506 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 504 can include a digital baseband interface to communicate with the RF circuitry 506.

[0069] In some dual-mode embodiments, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the

embodiments is not limited in this respect.

[0070] In some embodiments, the synthesizer circuitry 506d can be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 506d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0071] The synthesizer circuitry 506d can be configured to synthesize an output frequency for use by the mixer circuitry 506a of the RF circuitry 506 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 506d can be a fractional N/N+l synthesizer.

[0072] In some embodiments, frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a constraint. Divider control input can be provided by either the baseband circuitry 504 or the applications processor 502 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications processor 502.

[0073] Synthesizer circuitry 506d of the RF circuitry 506 can include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0074] In some embodiments, synthesizer circuitry 506d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency can be a LO frequency (fLO). In some embodiments, the RF circuitry 506 can include an IQ/polar converter.

[0075] FEM circuitry 508 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 510, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 506 for further processing. FEM circuitry 508 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 506 for transmission by one or more of the one or more antennas 510.

[0076] In some embodiments, the FEM circuitry 508 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 506). The transmit signal path of the FEM circuitry 508 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 506), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 510.

[0077] In some embodiments, the UE device 500 can include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface.

[0078] FIG. 6 illustrates a diagram 600 of a node 610 (e.g., eNB and/or a base station) and UE 620 in accordance with an example. The node can include a base station (BS), a NodeB (NB), an evolved NodeB (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a remote radio unit (RRU), or a central processing module (CPM). In one aspect, the node can be a Serving GPRS Support Node. The node 610 can include a node device 612. The node device 612 or the node 610 can be configured to communicate with the UE 620. The node device 612 can be configured to implement the technology described. The node device 612 can include a processing module 614 and a transceiver module 616. In one aspect, the node device 612 can include the transceiver module 616 and the processing module 614 forming a circuitry 618 for the node 610. In one aspect, the transceiver module 616 and the processing module 614 can form a circuitry of the node device 612. The processing module 614 can include one or more processors and memory. In one embodiment, the processing module 614 can include one or more application processors. The transceiver module 616 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 616 can include a baseband processor.

[0079] The UE 620 can include a transceiver module 624 and a processing module 622. The processing module 622 can include one or more processors and memory. In one embodiment, the processing module 622 can include one or more application processors. The transceiver module 624 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 624 can include a baseband processor. The UE 620 can be configured to implement the technology described. The node 610 and the UE 620 can also include one or more storage mediums, such as the transceiver module 616, 624 and/or the processing module 614, 622. In one aspect, the components described herein of the transceiver module 616 can be included in one or more separate devices that can be used in a cloud-RAN (C-RAN) environment.

[0080] FIG. 7 illustrates a diagram of a UE 700, in accordance with an example. In one aspect, the UE 700 can include at least one of an antenna 705, a touch sensitive display screen 710, a speaker 715, a microphone 720, a graphics processor 725, a baseband processor 730, an application processor 735, internal memory 740, a keyboard and/or one or more other keys, buttons, knobs and the like 745, a non-volatile memory port 750, and combinations thereof.

[0081] The UE 700 can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WW AN) access point. The one or more antennas of the UE 700 can also be configured to communicate with one or more other UEs. The UE 700 can be configured to communicate using at least one wireless

communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The UE 700 can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WW AN. The UE 700 can include a storage medium. In one aspect, the storage medium can be associated with and/or communicate with the application processor, the graphics processor, the display, the non-volatile memory port, and/or internal memory. In one aspect, the application processor and graphics processor are storage mediums.

EXAMPLES

[0082] The following examples pertain to specific technology embodiments and point out specific features, elements, or steps that can be used or otherwise combined in achieving such embodiments.

[0083] Example 1 includes an apparatus of an evolved NodeB (eNB) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), the apparatus comprising memory; and one or more processors configured to: encode, by an eNB, a capability inquiry message for transmission to a User Equipment (UE), wherein the eNB and UE are in a Radio Resource Control (RRC) connection and wherein a Radio Access Technology (RAT) type for the capability inquiry message is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); decode, by the eNB, a UE capability information message received from the UE, wherein the UE capability information message includes Information Elements (IEs) indicating whether the UE supports a legacy Quadrature Amplitude Modulation (QAM) or a 256QAM coding scheme; encode, by the eNB, a first signaling message including DL and UL MCS table information for transmission to the UE in response to the IEs indicating that the UE supports the 256QAM coding scheme; encode, by the eNB, a Downlink Control Information (DCI) format on a first set of Physical Downlink Control Channel (PDCCH) candidates to schedule 256QAM for Physical Uplink Shared Channel (PUSCH) transmission to the UE when the UE supports the 256QAM coding scheme; and decode, by the eNB, a PUSCH message received from the UE using the UL MCS table for the 256QAM coding scheme when the UE supports the 256QAM coding scheme. [0084] Example 2 includes the apparatus of Example 1, wherein the legacy QAM includes up to a 64QAM.

[0085] Example 3 includes the apparatus of Example 1, wherein the first set of PDCCH candidates are in UE-specific search space at least determined by a Cell Radio Network Temporary Identifier (C-RNTI) assigned for the UE and a slot number where the DCI format is monitored.

[0086] Example 4 includes the apparatus of Example 1, wherein the UL MCS table for the 256QAM coding scheme is a same size as the UL MCS table for the legacy QAM coding scheme and supports Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM.

[0087] Example 5 includes the apparatus of Examples 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a plurality of MCS entries reserved for indicating Redundancy Version (RV) of a PUSCH non-adaptive retransmission.

[0088] Example 6 includes the apparatus of Examples 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a full Signal -to-Noise Ratio (SNR) operation range of Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM.

[0089] Example 7 includes the apparatus of Examples 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a down-sampled low Signal-to- Interference-Noise Ratio (SINR) Quadrature Phase Shift Keying (QPSK) region of the legacy QAM coding scheme portion of the UL MCS table that has an even SINR space, and wherein the UL MCS table keeps one or more QPSK entries and does not include one or more duplicated MCS indices with duplicate Transport Block Size (TBS) indices from the legacy UL MCS table.

[0090] Example 8 includes the apparatus of Examples 1 or 4, wherein one or more new MCS entries with equal spacing fill an SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes and is less than that in a DL 256QAM MCS table.

[0091] Example 9 includes the apparatus of Example 1, wherein the one or more processors are further configured to: decode, by the eNB, the UE capability information message received from the UE, wherein the UE capability information message includes a DownLink (DL) 256QAM capability in a first IE and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

[0092] Example 10 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, by the eNB, the first signaling message as an UE dedicated RRC message.

[0093] Example 11 includes the apparatus of Example 10, wherein the UL MCS table and the DL MCS table are configured by one IE.

[0094] Example 12 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, by the eNB, the first signaling message including one DL MCS table information and one UL MCS table information that are selected from a plurality of DL MCS tables and UL MCS tables through one Radio Resource Control (RRC) message in accordance with the IEs indicating that the UE supports the 256QAM coding scheme from the UE.

[0095] Example 13 includes the apparatus of Example 12, wherein the UL

256QAM MCS table is configured for two subframes sets or a one subframe set, when the two subframe sets are configured for the UE.

[0096] Example 14 includes the apparatus of Example 1, wherein the one or more processors are further configured to: encode, by the eNB, the first signaling message in a Downlink Control Information (DCI) format including the UL MCS table information.

[0097] Example 15 includes the apparatus of Example 14, wherein the DCI format includes an UL MCS table identification to identify one MCS table from a plurality of MCS tables to determine modulation and coding for the PUSCH message.

[0098] Example 16 includes an An apparatus of a User Equipment (UE) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), the apparatus comprising memory; and one or more processors configured to: decode, by a UE, a capability inquiry message received from an evolved NodeB (eNB); determine, by the UE, a Radio Access Technology (RAT) type from the capability inquiry message; encode, by the UE, a UE capability information message including an indicator of a UL 256-order Quadrature Amplitude Modulation (256QAM) capability and another indicator of a DL 256QAM capability when the RAT type is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); decode, by the UE, a first signaling message received from the eNB, wherein the first signaling message includes an UL MCS information; determine, by the UE, an UL MCS table for a 256QAM coding scheme from a plurality of MCS tables based on the UL MCS information; and encode, by the UE, data for transmission on a Physical Uplink Shared Channel (PUSCH) using the UL MCS table for the 256QAM coding scheme if an associated Downlink Control Information (DCI) format is transmitted in a UE-specific Search Space (USS) in accordance with the first signaling message.

[0099] Example 17 includes the apparatus of Example 16, wherein the one or more processors are further configured to: determine, by the UE, a modulation order and a transport block size (TBS) using a legacy QAM coding scheme if the DCI format is transmitted in a Common Search Space (CSS).

[00100] Example 18 includes the apparatus of Example 16, wherein the plurality of MCS tables includes a Quadrature Phase Shift Keying (QPSK) MCS table, a 16QAM MCS table, a 64QAM MCS table, and the 256QAM MCS table.

[00101] Example 19 includes the apparatus of Example 16, wherein the plurality of MCS tables includes at least an UL MCS table that supports up to a 64QAM coding scheme and an UL MCS table that supports up to a 256QAM coding scheme.

[00102] Example 20 includes the apparatus of Example 19, wherein the UL MCS table that supports up to the 256QAM coding scheme includes: a table size the same as a table size of the UL MCS table that supports up to a 64 QAM coding scheme; a plurality of entries reserved to indicate a Redundancy Version (RV) of a PUSCH non-adaptive retransmission; a Signal-to-Noise Ratio (SNR) operational range of Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM; a down-sampled low Signal Interference Noise Ratio (SINR) QPSK region in a portion of the UL MCS table associated with up to 64 QAM support with an even SINR space that keeps one or more QPSK entries; one or more duplicated MCS indices with duplicate Transport Block Size (TBS) indices that are removed in a legacy UL MCS table portion; and a plurality of new MCS entries with equal spacing to fill an SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes. [00103] Example 21 includes the apparatus of Example 18, wherein a number of 256QAM entries in the UL MCS table for the 256QAM coding scheme is less than in a DownLink (DL) 256QAM MCS table.

[00104] Example 22 includes the apparatus of Example 16, wherein the one or more processors are further configured to: encode, by the UE, the UE capability information message, wherein the UE capability information message includes a

DownLink (DL) 256QAM capability in a first Information Element (IE) and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

[00105] Example 23 includes the apparatus of Example 16, wherein the first signaling message comprises an UE dedicated Radio Resource Control (RRC) message.

[00106] Example 24 includes the apparatus of Example 16, wherein the one or more processors are further configured to: decode, by the EU, the first signaling message including one DL MCS table information and one UL MCS table information selected through one RRC message.

[00107] Example 25 includes the apparatus of Example 16, wherein the UL 256QAM MCS table is configured for two subframes sets or a one subframe set, when the two subframe sets are configured for the UE.

[00108] Example 26 includes the apparatus of Example 16, wherein the UL MCS table and a downlink (DL) MCS table are configured by one Information Element (IE).

[00109] Example 27 includes the apparatus of Example 16, wherein the one or more processors are further configured to: decode, by the UE, the first signaling message in a Downlink Control Information (DCI) format including the UL MCS information.

[00110] Example 28 includes the apparatus of Example 26, wherein the one or more processors are further configured to: decode, by the UE, an UL MCS identifier included in a Downlink Control Information (DCI) format used for scheduling Physical Uplink Shared Channel (PUSCH) transmissions; and select, by the UE, the UL MCS table information, from a plurality of MCS tables, using the UL MCS identifier.

[00111] Example 29 includes the apparatus of Example 26, wherein the one or more processors are further configured to: decode, by the UE, a search space for a DCI format of 0 or 4; select, by the UE, an UL 64QAM MCS table if the DCI format of 0 or 4 is transmitted in a Common Search space (CSS); and select, by the UE, the UL MCS table for the 256QAM coding scheme if the DCI format of 0 or 4 is transmitted in a UE- specific Search Space (USS).

[00112] Example 30 includes the apparatus of Example 26, wherein the one or more processors are further configured to: determine, by the UE, an enhanced Physical Downlink Control Channel (ePDCCH) set index; select, by the UE, an UL 64QAM MCS table if a DCI format of 0 or 4 is transmitted in a first ePDCCH resource set; and select, by the UE, the UL MCS for the 256QAM coding scheme table if the DCI format of 0 or 4 is transmitted in a second ePDCCH resource set.

[00113] Example 31 includes the apparatus of Example 26, wherein the one or more processors are further configured to: determine, by the UE, a DCI format; select, by the UE, an UL 64QAM MCS table if the DCI format of 0 is determined; and select, by the UE, the UL MCS table for the 256QAM coding scheme if the DCI format of 4 is determined.

[00114] Example 32 includes the apparatus of Example 26, wherein the one or more processors are further configured to: determine, by the UE, a MCS table selection mark sequence used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format; select, by the UE, an UL 64QAM MCS table if a first MCS table selection mark sequence is determined; and select, by the UE, the UL MCS table for the 256QAM coding scheme if a second MCS table selection mark sequence is determined.

[00115] Example 33 includes the apparatus of Example 26, wherein the one or more processors are further configured to: determine, by the UE, a Cell Radio Network Topology Identifier (C-RNTI) value used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format; select, by the UE, an UL 61 QAM MCS table if a first C-RNTI value is determined; and select, by the UE, the UL MCS table for the 256QAM coding scheme if a second C-RNTI value is determined.

[00116] Example 34 includes the apparatus of Example 26, wherein the one or more processors are further configured to: determine, by the UE, an aggregation level used to transmit an UL DCI format; select, by the UE, an UL 64QAM MCS table if one of a first set of aggregation levels is determined; and select, by the UE, the UL MCS table for the 256QAM coding scheme if one of a second set of aggregation levels is determined.

[00117] Example 35 includes the apparatus of Example 16, wherein the one or more processors are further configured to: decode, by the UE, two sets of Uplink Control Information (UCI) offset parameters associated with different UL MCS tables; and determine, by the UE, a number of coded symbols or Resource Elements (REs) for UCIs on PUSCH based on a value of a corresponding UCI offset parameter that is associated with the determined UL MCS table for the 256QAM coding scheme.

[00118] Example 36 includes the apparatus of Example 35, wherein, a first set of UCI offset parameters is associated with an UL MCS table for a 64QAM coding scheme; and a second set of UCI offset parameters is linked to the UL MCS table for the 256QAM coding scheme or 256QAM entries in the UL MCS table for the 256QAM coding scheme.

[00119] Example 37 includes the apparatus of Example 35, wherein the UCI comprises at least hybrid automatic request repeat acknowledgment (HARQ-ACK),

Channel Quality Indicator (CQI), Rank Indicator (RI), and Beam selection Indicator (BI).

[00120] Example 38 includes the apparatus of Example 16, wherein the one or more processors are further configured to: encode, by the UE, the PUSCH message using different power compensator factor values associated with the UL MCS table for the 256QAM coding scheme, wherein a first value is associated with a 64QAM coding scheme portion of the UL MCS table and a second value is associated with a 256QAM coding scheme portion of the UL MCS table.

[00121] Example 39 includes an apparatus of an evolved NodeB (eNB) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS) comprising: a means for encoding, by an eNB, a capability inquiry message for transmission to a User Equipment (UE), wherein the eNB and UE are in a Radio Resource Control (RRC) connection and wherein a Radio Access Technology (RAT) type for the capability inquiry message is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); a means for decoding, by the eNB, a UE capability information message received from the UE, wherein the UE capability information message includes Information Elements (IEs) indicating whether the UE supports a legacy Quadrature Amplitude Modulation (QAM) or a 256QAM coding scheme; a means for encoding, by the eNB, a first signaling message including DL and UL MCS table information for transmission to the UE in response to the IEs indicating that the UE supports the 256QAM coding scheme; a means for encoding, by the eNB, a Downlink Control Information (DCI) format on a first set of Physical Downlink Control Channel (PDCCH) candidates to schedule 256QAM for

Physical Uplink Shared Channel (PUSCH) transmission to the UE when the UE supports the 256QAM coding scheme; and a means for decoding, by the eNB, a PUSCH message received from the UE using the UL MCS table for the 256QAM coding scheme when the UE supports the 256QAM coding scheme.

[00122] Example 40 includes the apparatus of Example 39, further comprising: a means for decoding, by the eNB, the UE capability information message received from the UE, wherein the UE capability information message includes a DownLink (DL) 256QAM capability in a first IE and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

[00123] Example 41 includes the apparatus of Example 39, further comprising: a means for encoding, by the eNB, the first signaling message as an UE dedicated RRC message.

[00124] Example 42 includes the apparatus of Example 39, further comprising: a means for encoding, by the eNB, the first signaling message including one DL MCS table information and one UL MCS table information that are selected from a plurality of DL MCS tables and UL MCS tables through one Radio Resource Control (RRC) message in accordance with the IEs indicating that the UE supports the 256QAM coding scheme from the UE.

[00125] Example 43 includes the apparatus of Example 39, further comprising: a means for encoding, by the eNB, the first signaling message in a Downlink Control Information (DCI) format including the UL MCS table information.

[00126] Example 44 includes an apparatus of a User Equipment (UE) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS) comprising: a means for decoding, by a UE, a capability inquiry message received from an evolved NodeB (eNB); a means for determining, by the UE, a Radio Access Technology (RAT) type from the capability inquiry message; a means for encoding, by the UE, a UE capability information message including an indicator of a UL 256-order Quadrature Amplitude Modulation (256QAM) capability and another indicator of a DL 256QAM capability when the RAT type is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); a means for decoding, by the UE, a first signaling message received from the eNB, wherein the first signaling message includes an UL MCS information; a means for determining, by the UE, an UL MCS table for a 256QAM coding scheme from a plurality of MCS tables based on the UL MCS information; and a means for encoding, by the UE, data for transmission on a Physical Uplink Shared Channel (PUSCH) using the UL MCS table for the 256QAM coding scheme if an associated Downlink Control Information (DCI) format is transmitted in a UE-specific Search Space (USS) in accordance with the first signaling message.

[00127] Example 45 includes the apparatus of Example 44, further comprising: a means for determining, by the UE, a modulation order and a transport block size (TBS) using a legacy QAM coding scheme if the DCI format is transmitted in a Common Search Space (CSS).

[00128] Example 46 includes the apparatus of Example 44, further comprising: a means for encoding, by the UE, the UE capability information message, wherein the UE capability information message includes a DownLink (DL) 256QAM capability in a first Information Element (IE) and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

[00129] Example 47 includes the apparatus of Example 44, further comprising: a means for decoding, by the EU, the first signaling message including one DL MCS table information and one UL MCS table information selected through one RRC message.

[00130] Example 48 includes the apparatus of Example 44, further comprising: a means for decoding, by the UE, the first signaling message in a Downlink Control Information (DCI) format including the UL MCS information.

[00131] Example 49 includes at least one machine readable storage medium having instructions embodied thereon for communicating data using an UpLink (UL) Modulation Coding Scheme (MCS), the instruction when executed perform the following: encoding, by an eNB, a capability inquiry message for transmission to a User Equipment (UE), wherein the eNB and UE are in a Radio Resource Control (RRC) connection and wherein a Radio Access Technology (RAT) type for the capability inquiry message is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); decoding, by the eNB, a UE capability information message received from the UE, wherein the UE capability information message includes Information Elements (IEs) indicating whether the UE supports a legacy Quadrature Amplitude Modulation (QAM) or a 256QAM coding scheme; encoding, by the eNB, a first signaling message including DL and UL MCS table information for transmission to the UE in response to the IEs indicating that the UE supports the 256QAM coding scheme; encoding, by the eNB, a Downlink Control Information (DCI) format on a first set of Physical Downlink Control Channel (PDCCH) candidates to schedule 256QAM for Physical Uplink Shared Channel (PUSCH) transmission to the UE when the UE supports the 256QAM coding scheme; and decoding, by the eNB, a PUSCH message received from the UE using the UL MCS table for the 256QAM coding scheme when the UE supports the 256QAM coding scheme.

[00132] Example 50 includes at least one machine readable storage medium having instructions embodied thereon for communicating data using an UpLink (UL) Modulation Coding Scheme (MCS), the instruction when executed perform the following: decoding, by a UE, a capability inquiry message received from an evolved NodeB (eNB);

determining, by the UE, a Radio Access Technology (RAT) type from the capability inquiry message; encoding, by the UE, a UE capability information message including an indicator of a UL 256-order Quadrature Amplitude Modulation (256QAM) capability and another indicator of a DL 256QAM capability when the RAT type is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); decoding, by the UE, a first signaling message received from the eNB, wherein the first signaling message includes an UL MCS information; determining, by the UE, an UL MCS table for a 256QAM coding scheme from a plurality of MCS tables based on the UL MCS information; and encoding, by the UE, data for transmission on a Physical Uplink Shared Channel (PUSCH) using the UL MCS table for the 256QAM coding scheme if an associated Downlink Control Information (DCI) format is transmitted in a UE-specific Search Space (USS) in accordance with the first signaling message.

[00133] As used herein, the term "circuitry" can refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, the circuitry can be implemented in, or functions associated with the circuitry can be implemented by, one or more software or firmware modules. In some aspects, circuitry can include logic, at least partially operable in hardware.

[00134] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, transitory or non- transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry can include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[00135] As used herein, the term processor can include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

[00136] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00137] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00138] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00139] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment. [00140] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as de facto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00141] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00142] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:

1. An apparatus of an evolved NodeB (eNB ) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), the apparatus comprising memory; and one or more processors configured to:

encode, by an eNB, a capability inquiry message for transmission to a User Equipment (UE), wherein the eNB and UE are in a Radio Resource Control (RRC) connection and wherein a Radio Access Technology (RAT) type for the capability inquiry message is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN); decode, by the eNB, a UE capability information message received from the UE, wherein the UE capability information message includes Information Elements (IEs) indicating whether the UE supports a legacy Quadrature Amplitude Modulation (QAM) or a 256QAM coding scheme;

encode, by the eNB, a first signaling message including DL and UL MCS table information for transmission to the UE in response to the IEs indicating that the UE supports the 256QAM coding scheme;

encode, by the eNB, a Downlink Control Information (DCI) format on a first set of Physical Downlink Control Channel (PDCCH) candidates to schedule 256QAM for Physical Uplink Shared Channel (PUSCH) transmission to the UE when the UE supports the 256QAM coding scheme; and

decode, by the eNB, a PUSCH message received from the UE using the UL MCS table for the 256QAM coding scheme when the UE supports the 256QAM coding scheme.

2. The apparatus of claim 1, wherein the legacy QAM includes up to a 64QAM.

3. The apparatus of claim 1, wherein the first set of PDCCH candidates are in UE- specific search space at least determined by a Cell Radio Network Temporary Identifier (C-RNTI) assigned for the UE and a slot number where the DCI format is monitored.

4. The apparatus of claim 1, wherein the UL MCS table for the 256QAM coding scheme is a same size as the UL MCS table for the legacy QAM coding scheme and supports Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM.

5. The apparatus of claims 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a plurality of MCS entries reserved for indicating Redundancy Version (RV) of a PUSCH non-adaptive retransmission.

6. The apparatus of claims 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a full Signal-to-Noise Ratio (SNR) operation range of Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM.

7. The apparatus of claims 1 or 4, wherein the UL MCS table for the 256QAM coding scheme includes a down-sampled low Signal-to-Interference-Noise Ratio (SINR) Quadrature Phase Shift Keying (QPSK) region of the legacy QAM coding scheme portion of the UL MCS table that has an even SINR space, and wherein the UL MCS table keeps one or more QPSK entries and does not include one or more duplicated MCS indices with duplicate Transport Block Size (TBS) indices from the legacy UL MCS table.

8. The apparatus of claims 1 or 4, wherein one or more new MCS entries with equal spacing fill an SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes and is less than that in a DL 256QAM MCS table.

9. The apparatus of claim 1, wherein the one or more processors are further configured to: decode, by the eNB, the UE capability information message received from the UE, wherein the UE capability information message includes a DownLink (DL) 256QAM capability in a first IE and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

10. The apparatus of claim 1, wherein the one or more processors are further configured to:

encode, by the eNB, the first signaling message as an UE dedicated RRC message.

11. The apparatus of claim 10, wherein the UL MCS table and the DL MCS table are configured by one IE.

12. The apparatus of claim 1, wherein the one or more processors are further configured to:

encode, by the eNB, the first signaling message including one DL MCS table information and one UL MCS table information that are selected from a plurality of DL MCS tables and UL MCS tables through one Radio Resource Control (RRC) message in accordance with the IEs indicating that the UE supports the 256QAM coding scheme from the UE.

13. The apparatus of claim 12, wherein the UL 256QAM MCS table is configured for two subframes sets or a one subframe set, when the two subframe sets are configured for the UE.

14. The apparatus of claim 1, wherein the one or more processors are further configured to:

encode, by the eNB, the first signaling message in a Downlink Control

Information (DCI) format including the UL MCS table information.

15. The method of claim 14, wherein the DCI format includes an UL MCS table identification to identify one MCS table from a plurality of MCS tables to determine modulation and coding for the PUSCH message.

16. An apparatus of a User Equipment (UE) operable to communicate data using an UpLink (UL) Modulation Coding Scheme (MCS), the apparatus comprising memory; and one or more processors configured to:

decode, by a UE, a capability inquiry message received from an evolved NodeB

(eNB);

determine, by the UE, a Radio Access Technology (RAT) type from the capability inquiry message;

encode, by the UE, a UE capability information message including an indicator of a UL 256-order Quadrature Amplitude Modulation (256QAM) capability and another indicator of a DL 256QAM capability when the RAT type is set to Evolved Universal Terrestrial Radio Access Network (E-UTRAN);

decode, by the UE, a first signaling message received from the eNB, wherein the first signaling message includes an UL MCS information;

determine, by the UE, an UL MCS table for a 256QAM coding scheme from a plurality of MCS tables based on the UL MCS information; and

encode, by the UE, data for transmission on a Physical Uplink Shared Channel

(PUSCH) using the UL MCS table for the 256QAM coding scheme if an associated Downlink Control Information (DCI) format is transmitted in a UE-specific Search Space (USS) in accordance with the first signaling message.

17. The apparatus of claim 16, wherein the one or more processors are further configured to:

determine, by the UE, a modulation order and a transport block size (TBS) using a legacy QAM coding scheme if the DCI format is transmitted in a Common Search Space (CSS).

18. The apparatus of claim 16, wherein the plurality of MCS tables includes a Quadrature Phase Shift Keying (QPSK) MCS table, a 16QAM MCS table, a 64QAM MCS table, and the 256QAM MCS table.

19. The apparatus of claim 16, wherein the plurality of MCS tables includes at least an UL MCS table that supports up to a 64QAM coding scheme and an UL MCS table that supports up to a 256QAM coding scheme.

20. The apparatus of claim 19, wherein the UL MCS table that supports up to the

256QAM coding scheme includes:

a table size the same as a table size of the UL MCS table that supports up to a 64 QAM coding scheme;

a plurality of entries reserved to indicate a Redundancy Version (RV) of a PUSCH non-adaptive retransmission;

a Signal-to-Noise Ratio (SNR) operational range of Quadrature Phase Shift Keying (QPSK), 16QAM, 64QAM and 256QAM;

a down-sampled low Signal Interference Noise Ratio (SINR) QPSK region in a portion of the UL MCS table associated with up to 64 QAM support with an even SINR space that keeps one or more QPSK entries;

one or more duplicated MCS indices with duplicate Transport Block Size (TBS) indices that are removed in a legacy UL MCS table portion; and

a plurality of new MCS entries with equal spacing to fill an SNR gap between an upper spectrum efficiency target of 64QAM and 256QAM coding schemes.

21. The apparatus of claim 18, wherein a number of 256QAM entries in the UL MCS table for the 256QAM coding scheme is less than in a DownLink (DL) 256QAM MCS table.

22. The apparatus of claim 16, wherein the one or more processors are further configured to:

encode, by the UE, the UE capability information message, wherein the UE capability information message includes a DownLink (DL) 256QAM capability in a first Information Element (IE) and a UL 256QAM capability in a second IE for each of a plurality of supported bands, or for a per band per band combination.

23. The apparatus of claim 16, wherein the first signaling message comprises an UE dedicated Radio Resource Control (RRC) message.

24. The apparatus of claim 16, wherein the one or more processors are further configured to:

decode, by the EU, the first signaling message including one DL MCS table information and one UL MCS table information selected through one RRC message.

25. The apparatus of claim 16, wherein the UL 256QAM MCS table is configured for two subframes sets or a one subframe set, when the two subframe sets are configured for the UE.

26. The apparatus of claim 16, wherein the UL MCS table and a downlink (DL) MCS table are configured by one Information Element (IE).

27. The apparatus of claim 16, wherein the one or more processors are further configured to:

decode, by the UE, the first signaling message in a Downlink Control Information (DCI) format including the UL MCS information.

28. The apparatus of claim 26, wherein the one or more processors are further configured to:

decode, by the UE, an UL MCS identifier included in a Downlink Control Information (DCI) format used for scheduling Physical Uplink Shared Channel (PUSCH) transmissions; and

select, by the UE, the UL MCS table information, from a plurality of MCS tables, using the UL MCS identifier.

29. The apparatus of claim 26, wherein the one or more processors are further configured to:

decode, by the UE, a search space for a DCI format of 0 or 4;

select, by the UE, an UL 64QAM MCS table if the DCI format of 0 or 4 is transmitted in a Common Search space (CSS); and

select, by the UE, the UL MCS table for the 256QAM coding scheme if the DCI format of 0 or 4 is transmitted in a UE-specific Search Space (USS).

30. The apparatus of claim 26, wherein the one or more processors are further configured to:

determine, by the UE, an enhanced Physical Downlink Control Channel

(ePDCCH) set index;

select, by the UE, an UL 64QAM MCS table if a DCI format of 0 or 4 is transmitted in a first ePDCCH resource set; and

select, by the UE, the UL MCS for the 256QAM coding scheme table if the DCI format of 0 or 4 is transmitted in a second ePDCCH resource set.

31. The apparatus of claim 26, wherein the one or more processors are further configured to:

determine, by the UE, a DCI format; select, by the UE, an UL 64QAM MCS table if the DCI format of 0 is determined; and

select, by the UE, the UL MCS table for the 256QAM coding scheme if the DCI format of 4 is determined.

32. The apparatus of claim 26, wherein the one or more processors are further configured to:

determine, by the UE, a MCS table selection mark sequence used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format;

select, by the UE, an UL 64QAM MCS table if a first MCS table selection mark sequence is determined; and

select, by the UE, the UL MCS table for the 256QAM coding scheme if a second MCS table selection mark sequence is determined.

33. The apparatus of claim 26, wherein the one or more processors are further configured to:

determine, by the UE, a Cell Radio Network Topology Identifier (C-RNTI) value used to scramble Cyclic Redundancy Check (CRC) bits of an UL DCI format;

select, by the UE, an UL 61 QAM MCS table if a first C-RNTI value is determined; and

select, by the UE, the UL MCS table for the 256QAM coding scheme if a second C-RNTI value is determined.

34. The apparatus of claim 26, wherein the one or more processors are further configured to:

determine, by the UE, an aggregation level used to transmit an UL DCI format; select, by the UE, an UL 64QAM MCS table if one of a first set of aggregation levels is determined; and select, by the UE, the UL MCS table for the 256QAM coding scheme if one of a second set of aggregation levels is determined.

35. The apparatus of claim 16, wherein the one or more processors are further configured to:

decode, by the UE, two sets of Uplink Control Information (UCI) offset parameters associated with different UL MCS tables; and

determine, by the UE, a number of coded symbols or Resource Elements (REs) for UCIs on PUSCH based on a value of a corresponding UCI offset parameter that is associated with the determined UL MCS table for the 256QAM coding scheme.

36. The apparatus of claim 35, wherein,

a first set of UCI offset parameters is associated with an UL MCS table for a 64QAM coding scheme; and

a second set of UCI offset parameters is linked to the UL MCS table for the 256QAM coding scheme or 256QAM entries in the UL MCS table for the 256QAM coding scheme.

37. The apparatus of claim 35, wherein the UCI comprises at least hybrid automatic request repeat acknowledgment (HARQ-ACK), Channel Quality Indicator (CQI), Rank Indicator (RI), and Beam selection Indicator (BI).

38. The apparatus of claim 16, wherein the one or more processors are further configured to:

encode, by the UE, the PUSCH message using different power compensator factor values associated with the UL MCS table for the 256QAM coding scheme, wherein a first value is associated with a 64QAM coding scheme portion of the UL MCS table and a second value is associated with a 256QAM coding scheme portion of the UL MCS table.