WO2022174135A1 - Techniques d'indication de schéma de modulation et de codage (mcs) - Google Patents

Techniques d'indication de schéma de modulation et de codage (mcs) Download PDF

Info

Publication number
WO2022174135A1
WO2022174135A1 PCT/US2022/016287 US2022016287W WO2022174135A1 WO 2022174135 A1 WO2022174135 A1 WO 2022174135A1 US 2022016287 W US2022016287 W US 2022016287W WO 2022174135 A1 WO2022174135 A1 WO 2022174135A1
Authority
WO
WIPO (PCT)
Prior art keywords
mcs
mcs table
entries
ntcrm
spectral efficiency
Prior art date
Application number
PCT/US2022/016287
Other languages
English (en)
Inventor
Dmitry DIKAREV
Alexei Davydov
Gregory Morozov
Daewon Lee
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to KR1020237031698A priority Critical patent/KR20230171922A/ko
Priority to CN202280025700.9A priority patent/CN117099333A/zh
Publication of WO2022174135A1 publication Critical patent/WO2022174135A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H04L1/0003—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes
    • H04L1/0005—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate by switching between different modulation schemes applied to payload information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H04L1/0011—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding applied to payload information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0016—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy involving special memory structures, e.g. look-up tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0025—Transmission of mode-switching indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/20—Arrangements for detecting or preventing errors in the information received using signal quality detector

Definitions

  • Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to modulation and coding scheme (MCS) indication.
  • MCS modulation and coding scheme
  • 5G New Radio supports dynamic adaptation of the transmission parameters to the actual link conditions. More specifically, depending on the channel state information (CSI), the next generation Node B (gNB) may indicate to the user equipment (UE) the optimal number of multiple input, multiple output (MIMO) layers and modulation and coding scheme (MCS) for physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission.
  • CSI channel state information
  • MIMO multiple input, multiple output
  • MCS modulation and coding scheme
  • Figure 1 illustrates spectral efficiency provided by modulation and coding scheme tables described herein, in accordance with various embodiments.
  • FIG. 2 illustrates spectral efficiencies associated with the MCS table of Table 5, in accordance with various embodiments.
  • FIG. 3 illustrates spectral efficiencies associated with the MCS table of Table 6, in accordance with various embodiments.
  • Figure 4 illustrates spectral efficiencies associated with the MCS table of Table 7, in accordance with various embodiments.
  • FIG. 5 illustrates spectral efficiencies associated with the MCS table of Table 8, in accordance with various embodiments.
  • Figure 6 illustrates spectral efficiencies associated with the MCS table of Table 9, in accordance with various embodiments.
  • Figure 7 illustrates spectral efficiency vs. SNR with uniform quantization of spectral efficiency range, in accordance with various embodiments.
  • Figure 8 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 9 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • FIG 11 illustrates a process of a user equipment (UE), in accordance with various embodiments.
  • FIG 12 illustrates a process of a next generation Node B (gNB), in accordance with various embodiments.
  • gNB next generation Node B
  • the MCS table may be for transmission of a physical downlink shared channel (PDSCH) and/or physical uplink shared channel (PUSCH) using two MIMO layers without MIMO layer adaptation.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the PDSCH and/or PUSCH may be transmitted in a sub-THz or THz channel, in which MIMO layer adaptation is not required.
  • 5GNew Radio supports dynamic adaptation of the transmission parameters to the actual link conditions. More specifically, depending on the channel state information (CSI), the next generation Node B (gNB) may indicate to the user equipment (UE) the optimal number of MIMO layers and modulation and coding scheme (MCS) for PDSCH or PUSCH transmission. The modulation order and the target coding rate is provided to the UE using MCS index.
  • MCS index is indicated to the UE by downlink control information (DCI) or radio resource control (RRC) (in case of configured grant transmission) signaling.
  • DCI downlink control information
  • RRC radio resource control
  • the MCS index refers to the row in the MCS table configured for the UE using RRC signaling.
  • MCS table 1 supporting modulation orders up to 64QAM
  • MCS table 2 supporting modulation orders up to 256QAM
  • Table 5.1.3.1-1 MCS index table 1 for PDSCH
  • the number of MIMO layers provide information on the number of spatial data streams that can be transmitted. It can be indicated implicitly (e.g. through demodulation reference signal (DM-RS) antenna port field) or explicitly. Based on the indicated MCS and number of MIMO layers, the UE determines transport block size (TBS) for PUSCH or PDSCH transmission based on the four steps procedure described in TS 38.214.
  • TBS transport block size
  • the current MCS table is not optimized assuming transmission using only two MIMO layers.
  • MIMO layer adaptation is not required for PDSCH and PUSCH transmission.
  • Various embodiments herein provide MCS table design assuming two MIMO layers transmission only.
  • the MCS table for two MIMO layers may be constructed by using the following procedure:
  • the reference MCS table may be MCS table 1 or 2 from TS 38.214 (e.g., as shown above).
  • the supported spectral efficiencies for enhanced MCS table are obtained by aggregating two sets of the spectral efficiencies. o The first set has total (across two MIMO layers) spectral efficiency which is the same as total spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2 from TS 38.214) with two MIMO layers.
  • the corresponding spectral efficiency from enhanced MCS table is associated with modulation orders which are the same as for corresponding MCS from the reference MCS table.
  • the second set has total (across two MIMO layers) spectral efficiency which is the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2 from TS 38.214) with one MIMO layer.
  • the spectral efficiency is not included in the second set if the difference with any spectral efficiency from the first set is less than pre-determined threshold, where threshold can be absolute or relative value.
  • ⁇ Spectral efficiency for enhanced MCS table is associated with modulation order which is the same as for corresponding MCS from the reference MCS table.
  • the first set of spectral efficiencies may correspond to the enhanced MCS table rows, whose modulation and code rate are reused from some rows of a reference MCS table.
  • the second set of spectral efficiencies may correspond to the new enhanced MCS table rows, whose modulation and code rate are chosen to reproduce the spectral efficiency (SE) of a reference MCS table with non-supported number of MIMO layers (e.g. rank 1).
  • SE spectral efficiency
  • Table 1 An example of the first embodiment is illustrated in Table 1, where the entries from the first set corresponds to MCS with indexes 3- 5, 7-8,10-11, 13-18, 20-21, 23-25, 27-37 while the entries from the second set is MCS indexes 0-2, 6, 9, 12, 19, 22, 26. MCS indexes from the reference MCS table is provided in the brackets of IMCS column for the first set.
  • the spectral efficiencies for enhanced MCS tables are obtained by aggregating two sets of the spectral efficiencies
  • the first set has total (across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with single MIMO layer o
  • the corresponding spectral efficiency from enhanced MCS table is associated with modulation orders which are the same as for corresponding MCS from the reference MCS table
  • the second set has total (across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with two MIMO layer and has spectral efficiencies higher than maximum spectral efficiency from the first set o
  • the corresponding spectral efficiency from enhanced MCS table is associated with modulation orders which are the same as for corresponding MCS from the reference MCS table
  • the first set of spectral efficiencies may correspond to the new enhanced MCS table rows, whose modulation and code rate are chosen to reproduce the spectral efficiency of a reference MCS table with non-supported number of MIMO layers (e.g. rank 1).
  • the second set of spectral efficiencies may correspond to the enhanced MCS table rows, whose modulation and code rate are reused from some rows of a reference MCS table.
  • the example of the second embodiment is illustrated in Table 2, where the entries from the first set is MCS with indexes 0 - 27, while the entries from the second set is MCS index 28 - 37.
  • the indexes from the reference MCS table is provided in the brackets.
  • enhanced MCS table include all spectral efficiencies supported by the reference MCS table for one and two MIMO layers with the same modulation orders.
  • the enhanced MCS table is used for 2 MIMO layer transmission.
  • the example of total spectral efficiencies, supported by MCS tables constructed from a reference MCS table using embodiments 1-3 is illustrated at Figure 1 (rows 3, 4).
  • the example of total spectral efficiencies, supported by the reference MCS table are shown for reference (rows 1, 2) ⁇
  • enhanced MCS table may also support pi/2 BPSK and 256QAM modulation.
  • spectral efficiencies for MCS with QPSK modulation order and coding rate less the pre-determined value e.g. 1/5
  • pre-determined value e.g. 1/5
  • additional spectral efficiencies can be supported by MCS with 256QAM modulation orders.
  • the associated spectral efficiency number for enhanced MCS table can be determined by the reference MCS Table 2.
  • MCS table supporting pi/2 BPSK, QSPK, 16QAM, 64QAM and 256QAM modulation designed according to the fourth embodiment is shown in Table 3, where pi/2 BPSK entries have MCS index of 0-3 and 256QAM entries have MCS index 40-47 in the enhanced MCS table. It should be noted that MCS with pi/BPSK modulation provides the same spectral efficiency as certain MCS with QPSK modulation. In the other embodiment, to reduce overhead, the corresponding QPSK entries can be removed to reduce MCS indication overhead.
  • MCS supporting pi/2 BPSK entries have MCS index of 0-3 and 256QAM entries have MCS index 42-49 in the enhanced MCS table.
  • MCS table for two MIMO layer transmission may be constructed by selecting target spectral efficiencies and modulation orders to provide: - substantially uniform grid of target SNR (in dB) corresponding to target BLER (e.g. 10%) of the corresponding MCS when used with a particular channel coding scheme;
  • the first example of the fifth embodiment is provided in Table 5, where 29 entries were assumed as available for explicit MCS indication.
  • the additional 3 entries may be used to support 256QAM modulation or implicit MCS indication for adaptive HARQ retransmission.
  • Table 5 The first example of the fifth embodiment
  • a second example of the fifth embodiment is provided in Table 6, where 32 entries were assumed as available with modulation orders of QPSK, 16QAM, 64QAM and 256QAM used to quantize the corresponding spectral efficiency range.
  • certain MCS entries associated with QPSK modulation and coding rate below threshold e.g. code rate of 1/5 can be replaced by pi/2 BPSK modulation order with two times higher coding rate.
  • the replacement of QPSK entries with pi/2 BPSK entries can be fixed in the specification or configured by higher layer.
  • the third example of the fifth embodiment is provided in Table 7, where 64 entries were assumed as available and modulation order of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency range.
  • some MCS entries associated with QPSK modulation and coding rate below threshold e.g. code rate of 1/5 has substantially similar / same spectral efficiency to MCS entries with pi/2 BPSK modulation.
  • the maximum spectral efficiency of certain modulation has similar / same value as minimum spectral efficiency of the next modulation order. Table 7
  • Table 7 The third example of the fifth embodiment
  • the fourth example of the fifth embodiment is provided in Table 8, where 64 entries were assumed as available and modulation order of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency range.
  • the spectal efficiency range is expanded to the low values (about 4 times lower than the lowest spectral efficiency supported in the third example of the embodiment, Table 7).
  • the fifth example of the fifth embodiment is provided in Table 9, where 64 entries were assumed as available and modulation order of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency range.
  • the example keeps the spectal efficiency range the same as in the third example of the embodiment (Table 7), while reducing the quantization step between the subsequent entries.
  • Table 9 The fifth example of the fifth embodiment
  • the approach, taken in the fifth embodiment, is reused.
  • the uniform grid of target SNR values (in dB) with the fixed SNR grid step
  • the uniform grid of provided spectral efficiencies (SEs) is used.
  • SEs spectral efficiencies
  • FIGS 8-10 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 8 illustrates a network 800 in accordance with various embodiments.
  • the network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.
  • the network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with a RAN 804 via an over-the-air connection.
  • the UE 802 may be communicatively coupled with the RAN 804 by a Uu interface.
  • the UE 802 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.
  • the network 800 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 802 may additionally communicate with an AP 806 via an over-the-air connection.
  • the AP 806 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 804.
  • the connection between the UE 802 and the AP 806 may be consistent with any IEEE 802.11 protocol, wherein the AP 806 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 802, RAN 804, and AP 806 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 802 being configured by the RAN 804 to utilize both cellular radio resources and WLAN resources.
  • the RAN 804 may include one or more access nodes, for example, AN 808.
  • AN 808 may terminate air-interface protocols for the UE 802 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 808 may enable data/voice connectivity between CN 820 and the UE 802.
  • the AN 808 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 808 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 808 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 804 may be coupled with one another via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 804 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 802 with an air interface for network access.
  • the UE 802 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 804.
  • the UE 802 and RAN 804 may use carrier aggregation to allow the UE 802 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 804 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 802 or AN 808 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 804 may be an LTE RAN 810 with eNBs, for example, eNB 812.
  • the LTE RAN 810 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 804 may be an NG-RAN 814 with gNBs, for example, gNB 816, or ng-eNBs, for example, ng-eNB 818.
  • the gNB 816 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 816 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 818 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 816 and the ng-eNB 818 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 814 and a UPF 848 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN814 and an AMF 844 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 814 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 802 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 802 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 802 and in some cases at the gNB 816.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 804 is communicatively coupled to CN 820 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 802).
  • the components of the CN 820 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 820 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 820 may be referred to as a network slice, and a logical instantiation of a portion of the CN 820 may be referred to as a network sub-slice.
  • the CN 820 may be an LTE CN 822, which may also be referred to as an EPC.
  • the LTE CN 822 may include MME 824, SGW 826, SGSN 828, HSS 830, PGW 832, and PCRF 834 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 822 may be briefly introduced as follows.
  • the MME 824 may implement mobility management functions to track a current location of the UE 802 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 826 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 822.
  • the SGW 826 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 828 may track a location of the UE 802 and perform security functions and access control. In addition, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 824; MME selection for handovers; etc.
  • the S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states.
  • the HSS 830 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 830 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 830 and the MME 824 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 820.
  • the PGW 832 may terminate an SGi interface toward a data network (DN) 836 that may include an application/content server 838.
  • the PGW 832 may route data packets between the LTE CN 822 and the data network 836.
  • the PGW 832 may be coupled with the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 832 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 832 and the data network 8 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 832 may be coupled with a PCRF 834 via a Gx reference point.
  • the PCRF 834 is the policy and charging control element of the LTE CN 822.
  • the PCRF 834 may be communicatively coupled to the app/content server 838 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 832 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 820 may be a 5GC 840.
  • the 5GC 840 may include an AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, and AF 860 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 840 may be briefly introduced as follows.
  • the AUSF 842 may store data for authentication of UE 802 and handle authentication- related functionality.
  • the AUSF 842 may facilitate a common authentication framework for various access types.
  • the AUSF 842 may exhibit an Nausf service-based interface.
  • the AMF 844 may allow other functions of the 5GC 840 to communicate with the UE 802 and the RAN 804 and to subscribe to notifications about mobility events with respect to the UE 802.
  • the AMF 844 may be responsible for registration management (for example, for registering UE 802), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization.
  • the AMF 844 may provide transport for SM messages between the UE 802 and the SMF 846, and act as a transparent proxy for routing SM messages.
  • AMF 844 may also provide transport for SMS messages between UE 802 and an SMSF.
  • AMF 844 may interact with the AUSF 842 and the UE 802 to perform various security anchor and context management functions.
  • AMF 844 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 804 and the AMF 844; and the AMF 844 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 844 may also support NAS signaling with the UE 802 over an N3 IWF interface.
  • the SMF 846 may be responsible for SM (for example, session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 848 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 844 over N2 to AN 808; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 802 and the data network 836.
  • the UPF 848 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 836, and a branching point to support multi-homed PDU session.
  • the UPF 848 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 848 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 850 may select a set of network slice instances serving the UE 802.
  • the NSSF 850 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 850 may also determine the AMF set to be used to serve the UE 802, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 854.
  • the selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 with which the UE 802 is registered by interacting with the NSSF 850, which may lead to a change of AMF.
  • the NSSF 850 may interact with the AMF 844 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 850 may exhibit an Nnssf service-based interface.
  • the NEF 852 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 860), edge computing or fog computing systems, etc.
  • the NEF 852 may authenticate, authorize, or throttle the AFs.
  • NEF 852 may also translate information exchanged with the AF 860 and information exchanged with internal network functions. For example, the NEF 852 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 852 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 852 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 852 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 852 may exhibit an Nnef service-based interface.
  • the NRF 854 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 854 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 854 may exhibit the Nnrf service-based interface.
  • the PCF 856 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 856 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 858.
  • the PCF 856 exhibit an Npcf service-based interface.
  • the UDM 858 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 802. For example, subscription data may be communicated via an N8 reference point between the UDM 858 and the AMF 844.
  • the UDM 858 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 858 and the PCF 856, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 802) for the NEF 852.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 858, PCF 856, and NEF 852 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 858 may exhibit the Nudm service-based interface.
  • the AF 860 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 840 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 802 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 840 may select a UPF 848 close to the UE 802 and execute traffic steering from the UPF 848 to data network 836 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 860. In this way, the AF 860 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 860 to interact directly with relevant NFs. Additionally, the AF 860 may exhibit an Naf service-based interface.
  • the data network 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 838.
  • FIG. 9 schematically illustrates a wireless network 900 in accordance with various embodiments.
  • the wireless network 900 may include a UE 902 in wireless communication with an AN 904.
  • the UE 902 and AN 904 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 902 may be communicatively coupled with the AN 904 via connection 906.
  • the connection 906 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 902 may include a host platform 908 coupled with a modem platform 910.
  • the host platform 908 may include application processing circuitry 912, which may be coupled with protocol processing circuitry 914 of the modem platform 910.
  • the application processing circuitry 912 may run various applications for the UE 902 that source/sink application data.
  • the application processing circuitry 912 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 914 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 906.
  • the layer operations implemented by the protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 914 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and RF front end (RFFE) 924, which may include or connect to one or more antenna panels 926.
  • the transmit circuitry 918 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 920 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 922 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 924 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914.
  • the antenna panels 926 may receive a transmission from the AN 904 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 926.
  • a UE transmission may be established by and via the protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panels 926.
  • the transmit components of the UE 904 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 926.
  • the AN 904 may include a host platform 928 coupled with a modem platform 930.
  • the host platform 928 may include application processing circuitry 932 coupled with protocol processing circuitry 934 of the modem platform 930.
  • the modem platform may further include digital baseband circuitry 936, transmit circuitry 938, receive circuitry 940, RF circuitry 942, RFFE circuitry 944, and antenna panels 946.
  • the components of the AN 904 may be similar to and substantially interchangeable with like-named components of the UE 902.
  • the components of the AN 908 may perform various logical functions that include, for example,
  • RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 10 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 10 shows a diagrammatic representation of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory/storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry.
  • a hypervisor 1002 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1000.
  • the processors 1010 may include, for example, a processor 1012 and a processor 1014.
  • the processors 1010 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radio- frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1020 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1030 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1006 or other network elements via a network 1008.
  • the communication resources 1030 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 1050 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1010 to perform any one or more of the methodologies discussed herein.
  • the instructions 1050 may reside, completely or partially, within at least one of the processors 1010 (e.g., within the processor’s cache memory), the memory/storage devices 1020, or any suitable combination thereof.
  • any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral devices 1004 or the databases 1006. Accordingly, the memory of processors 1010, the memory/storage devices 1020, the peripheral devices 1004, and the databases 1006 are examples of computer-readable and machine-readable media.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 8-10, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • One such process 1100 is depicted in Figure 11.
  • the process 1100 may be performed by a UE or a portion thereof.
  • the process 1100 may include receiving a modulation and coding scheme (MCS) index.
  • MCS modulation and coding scheme
  • the process 1100 may further include determining, based on an entry in a MCS table that corresponds to the MCS index, a modulation order, a code rate, and a spectral efficiency for a transmission, wherein the MCS table is for a fixed number of multiple input, multiple output (MIMO) layers without MIMO layer adaptation.
  • MIMO multiple input, multiple output
  • the fixed number may be 2 or another suitable number of MIMO layers.
  • the process may further include transmitting or receiving the transmission based on the modulation order, the code rate, and the spectral efficiency.
  • FIG. 12 illustrates another process 1200 in accordance with various embodiments.
  • the process 1200 may be performed by a gNB or a portion thereof.
  • the process 1200 may include determining an entry in a modulation and coding scheme (MCS) table for a transmission with a fixed number of multiple input multiple output (MIMO) layers without MIMO layer adaptation, wherein the entry includes an MCS index, a modulation order, a code rate, and a spectral efficiency.
  • the fixed number may be 2 or another suitable number of MIMO layers.
  • the process 1200 may further include transmitting the MCS index to a user equipment (UE).
  • the process 1200 may further include transmitting or receiving the transmission based on the modulation order, the code rate, and the spectral efficiency.
  • MCS modulation and coding scheme
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example A1 may include one or more non-transitory, computer-readable media (NTCRM) having instructions stored thereon that, when executed, cause a user equipment (UE) to: receive a modulation and coding scheme (MCS) index; determine, based on an entry in a MCS table that corresponds to the MCS index, a modulation order, a code rate, and a spectral efficiency for a transmission, wherein the MCS table is for a fixed number of multiple input, multiple output (MIMO) layers without MIMO layer adaptation; and transmit or receive the transmission based on the modulation order, the code rate, and the spectral efficiency.
  • NCRM non-transitory, computer-readable media
  • Example A2 may include the one or more NTCRM of example Al, wherein the MCS table includes a plurality of entries that correspond to respective MCS indexes, and wherein there is at least one entry for which the respective modulation order is each of pi/2 binary phase- shift keying (BPSK), quadrature phase-shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64 QAM, and 256 QAM.
  • BPSK binary phase- shift keying
  • QPSK quadrature phase-shift keying
  • QAM 16 quadrature amplitude modulation
  • 64 QAM 64 QAM
  • 256 QAM 256 QAM
  • Example A3 may include the one or more NTCRM of example A2, wherein there are 64 entries in the MCS table.
  • Example A4 may include the one or more NTCRM of example Al, wherein the MCS table includes a plurality of entries that correspond to respective MCS indexes, and wherein the entries of the MCS table combine to provide: a substantially uniform grid of target signal-to- noise ratio (SNR.) corresponding to a target block error rate (BLER) of the corresponding MCS or a substantially uniform grid of spectral efficiencies of the corresponding MCS when used with a particular channel coding scheme; a combination of the code rate and the modulation order for the corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and a number of the entries that is required to keep a bitwidth of a MCS field in a downlink control information at or below a predefined value.
  • SNR. target signal-to- noise ratio
  • BLER target block error rate
  • Example A5 may include the one or more NTCRM of example A4, wherein the entries of the MCS table combine to further provide maximum and minimum SNRs corresponding to a target BLER for the MCSs so that an absolute value of a decibel difference between the maximum or minimum SNR corresponding to the target BLER in the MCS table and a respective maximum or minimum SNR corresponding to the target BLER in a reference MCS table is smaller than the uniform SNR grid step provided by the MCS table.
  • Example A6 may include the one or more NTCRM of example A5, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 vl6.4.0 for 1 or 2 MIMO layers.
  • Example A7 may include the one or more NTCRM of example A3, wherein the entries of the MCS table combine to further provide an SNR grid step below a threshold.
  • Example A8 may include the one or more NTCRM of any one of examples A1 to A7, wherein the MCS table is: wherein IMCS is the MCS index, Qm is the modulation order, R is the code rate, and per layer spectral efficiency (SE) is the spectral efficiency per MIMO layer.
  • MCS table is: wherein IMCS is the MCS index, Qm is the modulation order, R is the code rate, and per layer spectral efficiency (SE) is the spectral efficiency per MIMO layer.
  • Example A9 may include the one or more NTCRM of any one of examples A1 to A7, wherein the fixed number is 2.
  • Example A10 may include an apparatus of a user equipment (UE), the apparatus comprising: a memory to store a modulation and coding scheme (MCS) table for two multiple input multiple output (MIMO) layers, wherein the MCS table includes: a first set of entries with total spectral efficiencies and associated modulation orders that are the same as corresponding entries of a reference MCS table with two MIMO layers; and a second set of entries with total spectral efficiencies and associated modulation orders that are the same as corresponding entries of the reference MCS table with one MIMO layer.
  • MCS modulation and coding scheme
  • the apparatus may further include processor circuitry coupled to the memory, the processor circuitry to: receive a MCS index; determine, based on the MCS index and the MCS table, a modulation order, a code rate, and a spectral efficiency for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH); and encode the PUSCH for transmission or decode the PDSCH based on the modulation order, the code rate, and the spectral efficiency.
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • Example A11 may include the apparatus of example A10, wherein an entry of the reference MCS table with one MIMO layer is not included in the second set if a difference between the spectral efficiency of the entry and any entry from the first set of entries is less than a pre-determined threshold.
  • Example A12 may include the apparatus of example All, wherein the threshold is an absolute value or a relative value.
  • Example A13 may include the apparatus of example A10, wherein the second set of entries have a respective modulation order and a code rate to reproduce the corresponding spectral efficiency of the reference MCS table with one MIMO layer.
  • Example A14 may include the apparatus of example A10, wherein the PDSCH or PUSCH is transmitted without MIMO layer adaptation.
  • Example A15 may include the apparatus of any one of examples A10 to A14, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 V16.4.0.
  • the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 V16.4.0.
  • Example A16 may include one or more non-transitory, computer-readable media (NTCRM) having instructions stored thereon that, when executed, cause a next generation Node B (gNB) to: determine an entry in a modulation and coding scheme (MCS) table for a transmission with a fixed number of multiple input multiple output (MIMO) layers without MIMO layer adaptation, wherein the entry includes an MCS index, a modulation order, a code rate, and a spectral efficiency; transmit the MCS index to a user equipment (UE); and transmit or receive the transmission based on the modulation order, the code rate, and the spectral efficiency.
  • NCRM non-transitory, computer-readable media
  • Example A17 may include the one or more NTCRM of example A16, wherein the MCS table includes a plurality of entries that correspond to respective MCS indexes, and wherein there is at least one entry for which the respective modulation order is each of pi/2 binary phase- shift keying (BPSK), quadrature phase-shift keying (QPSK), 16 quadrature amplitude modulation (QAM), 64 QAM, and 256 QAM.
  • BPSK binary phase- shift keying
  • QPSK quadrature phase-shift keying
  • QAM 16 quadrature amplitude modulation
  • 64 QAM 64 QAM
  • 256 QAM 256 QAM
  • Example A18 may include the one or more NTCRM of example A17, wherein there are 64 entries in the MCS table.
  • Example A19 may include the one or more NTCRM of example A16, wherein the MCS table includes a plurality of entries that correspond to respective MCS indexes, and wherein the entries of the MCS table combine to provide: a substantially uniform grid of target signal-to- noise ratio (SNR.) corresponding to a target block error rate (BLER) of the corresponding MCS or a substantially uniform grid of spectral efficiencies of the corresponding MCS when used with a particular channel coding scheme; a combination of the code rate and the modulation order for the corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and a number of the entries that is required to keep a bitwidth of a MCS field in a downlink control information at or below a predefined value.
  • SNR. target signal-to- noise ratio
  • BLER target block error rate
  • Example A20 may include the one or more NTCRM of example A19, wherein the entries of the MCS table combine to further provide maximum and minimum SNRs corresponding to a target BLER for the MCSs so that an absolute value of a decibel difference between the maximum or minimum SNR corresponding to the target BLER in the MCS table and a respective maximum or minimum SNR corresponding to the target BLER in a reference MCS table is smaller than the uniform SNR grid step provided by the MCS table.
  • Example A21 may include the one or more NTCRM of example A20, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 vl6.4.0 for 1 or 2 MIMO layers.
  • TS Technical Standard
  • Example A22 may include the one or more NTCRM of example A19, wherein the entries of the MCS table combine to further provide an SNR grid step below a threshold.
  • Example A23 may include the one or more NTCRM of any one of examples A16 to A22, wherein the MCS table is: wherein IMCS is the MCS index, Qm is the modulation order, R is the code rate, and per layer spectral efficiency (SE) is the spectral efficiency per MIMO layer.
  • MCS table is: wherein IMCS is the MCS index, Qm is the modulation order, R is the code rate, and per layer spectral efficiency (SE) is the spectral efficiency per MIMO layer.
  • Example A24 may include the one or more NTCRM of any one of examples A16 to A22, wherein the fixed number is 2.
  • Example B1 may include a method of enhanced MCS table construction, wherein the method includes determining the reference set of supported spectral efficiencies by the reference MCS table with one and multiple MIMO layers; and defining a new MCS table that supports substantial number of the reference spectral efficiencies with fixed number of MIMO layers, wherein some of the reference spectral efficiencies can be approximated by similar value from the enhanced MCS table.
  • Example B2 may include the method of example B1 or some other example herein, wherein multiple MIMO layers corresponds to two MIMO layers.
  • Example B3 may include the method of example B1 or some other example herein, wherein fixed number of MIMO layers corresponds to two MIMO layers.
  • Example B4 may include the method of example B1 or some other example herein, wherein the supported spectral efficiencies for enhanced MCS table are obtained by aggregating two sets of the spectral efficiencies.
  • Example B5 may include the method of example B4 or some other example herein, wherein the first set has total (e.g., across two MIMO layers) spectral efficiency which is the same as total spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with two MIMO layers and the second set has total (e.g., across two MIMO layers) spectral efficiency which is the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with one MIMO layer, wherein the spectral efficiency is not included in the second set if the difference with any spectral efficiency from the first set is less than pre determined threshold, where threshold can be absolute or relative value.
  • the first set has total (e.g., across two MIMO layers) spectral efficiency which is the same as total spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with two MIMO layers
  • the second set has total (e.g., across two M
  • Example B6 may include the method of example B4 or some other example herein, wherein the first set has total (e.g., across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with single MIMO layer and the second set has total (e.g., across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with two MIMO layer and has spectral efficiencies higher than maximum spectral efficiency from the first set.
  • the first set has total (e.g., across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or MCS table 2) with single MIMO layer and the second set has total (e.g., across two layers) spectral efficiencies which are the same as spectral efficiency of the reference MCS table (e.g., MCS table 1 or
  • Example B7 may include the method of examples B5 or B6 or some other example herein, wherein the corresponding spectral efficiency from enhanced MCS table is associated with modulation orders which are the same as for corresponding MCS from the reference MCS table.
  • Example B8 may include the method of example B1 or some other example herein, wherein enhanced MCS table include all spectral efficiencies supported by the reference MCS table for one and two MIMO layers with the same modulation orders.
  • Example B9 may include the method of examples B1 or B4 or some other example herein, wherein MCS table also include MCS with pi/2 BPSK modulation with the same spectral efficiencies as MCS entries with QPSK modulation and the coding rate below predetermined value.
  • Example BIO may include the system and method of example B9 or some other example herein, wherein predetermined value of code rate is 1/5.
  • Example B11 may include a method of enhanced MCS table construction, wherein the method includes: selecting the target spectral efficiencies and modulation orders that provides substantially uniform grid of target SNR (signal to noise ratio) for transmission with fixed number of MIMO layers corresponding to fixed BLER (block error rate) of the corresponding MCS; selecting the target minimal and maximal spectral efficiencies supported by MCS table; and selecting the SNR step of the uniform grid of target SNR.
  • target SNR signal to noise ratio
  • BLER block error rate
  • Example B12 may include a method of enhanced MCS table construction, wherein the method includes: selecting the target spectral efficiencies and modulation orders that provides substantially uniform grid of spectral efficiencies for transmission with fixed number of MIMO layers; selecting the target minimal and maximal spectral efficiencies supported by MCS table; and selecting the spectral efficiency step of the uniform spectral efficiency grid.
  • Example B13 may include the method of example B11 or some other example herein, wherein the BLER of the corresponding MCS is measured using LDPC channel coding scheme.
  • Example B14 may include the method of examples B11 or B 12 or some other example herein, wherein the minimal and maximal spectral efficiencies are selected in order to be almost the same as minimal and maximal spectral efficiencies of the reference MCS table, where the reference MCS table is MCS table 1 and / or MCS table 2 defined in TS 38.214 for 1 and 2 MIMO layers.
  • Example B15 may include the method of examples B11 or B 12 or some other example herein, wherein the minimal and maximal spectral efficiencies are selected in order to the target maximum and minimum SNR supported by the MCS table are almost the same as maximum and minimum SNR of the reference MCS table, where the reference MCS table is MCS table 1 and / or MCS table 2 defined in TS 38.214 for 1 and 2 MIMO layers.
  • Example B16 may include the method of example B11 or some other example herein, wherein the SNR grid step is selected in order to achieve a predefined DCI MCS field bitwidth.
  • Example B17 may include the method of example B 12 or some other example herein, wherein the SE grid step is selected in order to achieve a predefined DCI MCS field bitwidth.
  • Example B18 may include the method of example B11 or some other example herein, wherein MCS table is according to Table 5.
  • Example B19 may include the method of example B11 or some other example herein, wherein MCS table is according to Table 6.
  • Example B20 may include the method of example B 11 or some other example herein, wherein MCS table is according to Table 7.
  • Example B21 may include the method of examples B11 or B 12 or some other example herein, wherein MCS entries supporting pi / 2 BPSK provide similar or same spectral efficiency to subset of MCS entries supporting QPSK modulation.
  • Example B22 may include the method of example B 11 or some other example herein, wherein MCS table is according to Table 8.
  • Example B23 may include the method of example B11 or some other example herein, wherein MCS table is according to Table 9.
  • Example B24 may include system and method of examples B11 or B 12 or some other example herein, wherein MCS entries supporting pi / 2 BPSK provide similar or same spectral efficiency to subset of MCS entries supporting QPSK modulation.
  • Example B25 may include a method comprising: determining one or more parameters for transmission of a signal based on one or more of the MCS tables herein; and encoding or decoding the signal based on the determined one or more parameters.
  • Example B26 may include the method of example B25 or some other example herein, wherein the one or more parameters are determined based on an MCS index.
  • Example B27 may include the method of example B25-B26 or some other example herein, wherein the one or more parameters include a transport block size, a number of layers, and/or a spectral efficiency.
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples A1-A24, B1-B27 or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples A1-A24, B1-B27, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples A1-A24, B1-B27 or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples A1-A24, B1-B27 or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25 or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples A1-A24, B1-B27 or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A1-A24, B1-B27 or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples A1-A24, B1-B27 or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples A1-A24, Bl- B27, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples A1-A24, B1-B27 or portions thereof.
  • Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples A1-A24, Bl- B27 or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • AMBRAggregate 60 Authenticatio Identity Maximum Bit Rate n Server 95
  • CPE Customer CSI Channel-State Cl Cell Identity Premise Information
  • CID Cell-ID e g., Equipment CSI-IM CSI positioning 65 CPICHCommon 100 Interference method Pilot Channel Measurement
  • CSI-SINR CSI 40 DMTF Distributed Network signal-to-noise and Management Task E2E End-to-End interference Force 75 ECCA extended clear ratio DPDK Data Plane channel
  • Enabler Server EPC Evolved Evolved EESID Edge Packet Core UTRAN
  • Register resource Channel/Full eLAA enhanced element groups rate Licensed Assisted ETSI European FACCH/H Fast Access, Telecommuni Associated Control enhanced LAA 60 cations 95 Channel/Half EM Element Standards rate Manager Institute FACH Forward eMBB Enhanced ETWS Earthquake Access Channel Mobile and Tsunami FAUSCH Fast
  • FDD Frequency G-RNTI GNSS Global Division Duplex GERAN Navigation Satellite
  • FDM Frequency Radio Network System Division 45 Temporary 80 GPRS
  • NodeB GUTI Globally HTTP Hyper Text IEI Information Unique Temporary 35 Transfer Element UE Identity Protocol 70 Identifier HARQ Hybrid ARQ, HTTPS Hyper IEIDL Information Hybrid Text Transfer Element
  • Packet Access IDFT Inverse identity HSN Hopping Discrete Fourier IMPI IP Multimedia Sequence Number Transform Private HSPA High Speed 60 IE Information Identity Packet Access element 95 IMPU IP Multimedia HSS Home IBE In-Band PUblic Subscriber Server Emission identity HSUPA High IEEE Institute of IMS IP Multimedia
  • IP-CAN IP- 45 (1000 bytes) 80 LBT Listen Before Connectivity Access kbps kilo-bits per Talk Network second LCM LifeCycle
  • ISIM IM Services 60 ksps kilo-symbols 95 LPLMN Local Identity Module per second PLMN ISO International KVM Kernel Virtual LPP LTE Organisation for Machine Positioning Protocol Standardisation LI Layer 1 LSB Least ISP Internet 65 (physical layer) 100 Significant Bit Service Provider Ll-RSRP Layer LTE Long Term IWF Interworking- 1 reference signal Evolution Function received LWA LTE-WLAN power aggregation LWIP LTE/WLAN Multicast MGRP Measurement Radio Level Service Gap Repetition
  • M2M Machine-to- Frequency MIMO Multiple Input Machine Network Multiple Output MAC Medium 45 MCC Mobile 80 MLC Mobile Access Control Country Code Location Centre (protocol MCG Master Cell MM Mobility layering context) Group Management MAC Message MCOT Maximum MME Mobility authentication code 50 Channel 85 Management Entity (security/ encry pti on Occupancy MN Master Node context) Time MNO Mobile
  • Access Identifier Orchestrator MCH Scheduling NAS Non-Access 85 NG Next Information Stratum, Non- Generation, Next Gen MSID Mobile Access NGEN-DC NG- Station Identifier 55 Stratum layer RAN E-UTRA-NR MSIN Mobile NCT Network Dual Connectivity Station Connectivity 90 NM Network
  • NEC Network 95 N-PoP Network Number Capability Point of Presence MT Mobile Exposure NMIB, N-MIB Terminated, Mobile 65 NE-DC NR-E- Narrowband MIB Termination UTRA Dual NPBCH MTC Machine- Connectivity 100 Narrowband Type Physical Broadcast 35 NRS Narrowband 70 OFDMA CHannel Reference Signal Orthogonal NPDCCH NS Network Frequency
  • Modulation number (used for 85 Failure QCI QoS class of authentication RLM Radio Link identifier ) Monitoring
  • S-RNTI SRNC SCG Secondary RS Reference Radio Network Cell Group Signal Temporary SCM Security
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer- executable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • user equipment or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • user equipment or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/sy stems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .
  • SSB refers to an SS/PBCH block.
  • Primary Cell refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Secondary Cell refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA /.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Landscapes

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

Abstract

La présente invention concerne, selon divers modes de réalisation, des techniques pour la conception d'une table de schémas de modulation et de codage (MCS) dans un système cellulaire sans fil. La table de MCS peut être optimisée pour une transmission à deux couches à entrées et sorties multiples (MIMO), p.ex. sans adaptation de couche MIMO. D'autres modes de réalisation peuvent être décrits et revendiqués.
PCT/US2022/016287 2021-02-15 2022-02-14 Techniques d'indication de schéma de modulation et de codage (mcs) WO2022174135A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020237031698A KR20230171922A (ko) 2021-02-15 2022-02-14 변조 및 코딩 방식(mcs) 표시를 위한 기술들
CN202280025700.9A CN117099333A (zh) 2021-02-15 2022-02-14 用于调制和编码方案（mcs）指示的技术

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163149529P 2021-02-15 2021-02-15
US63/149,529 2021-02-15
US202163155243P 2021-03-01 2021-03-01
US63/155,243 2021-03-01

Publications (1)

Publication Number Publication Date
WO2022174135A1 true WO2022174135A1 (fr) 2022-08-18

Family

ID=82837349

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/016287 WO2022174135A1 (fr) 2021-02-15 2022-02-14 Techniques d'indication de schéma de modulation et de codage (mcs)

Country Status (2)

Country Link
KR (1) KR20230171922A (fr)
WO (1) WO2022174135A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215913A1 (en) * 2014-01-30 2015-07-30 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods utilizing an efficient tbs table design for 256qam in a cellular communications network
US20180368108A1 (en) * 2017-06-16 2018-12-20 Qualcomm Incorporated Multiple mcs tables for nr
US20200213033A1 (en) * 2017-09-13 2020-07-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data processing method, terminal device and network device
US20200252113A1 (en) * 2018-02-20 2020-08-06 Apple Inc. Transport block selection for 1024 quadrature amplitude modulation (qam)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215913A1 (en) * 2014-01-30 2015-07-30 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods utilizing an efficient tbs table design for 256qam in a cellular communications network
US20180368108A1 (en) * 2017-06-16 2018-12-20 Qualcomm Incorporated Multiple mcs tables for nr
US20200213033A1 (en) * 2017-09-13 2020-07-02 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Data processing method, terminal device and network device
US20200252113A1 (en) * 2018-02-20 2020-08-06 Apple Inc. Transport block selection for 1024 quadrature amplitude modulation (qam)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 16)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.214, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. V16.4.0, 8 January 2021 (2021-01-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 169, XP051999688 *

Also Published As

Publication number Publication date
KR20230171922A (ko) 2023-12-21

Similar Documents

Publication Publication Date Title
US11902985B2 (en) Default PDSCH beam setting and PDCCH prioritization for multi panel reception
US20220272706A1 (en) Downlink control information (dci) based beam indication for wireless cellular network
US20230239122A1 (en) Frequency hopping and collision handling for uplink transmission in advanced duplex systems
WO2022212688A1 (fr) Commutation entre des configurations de surveillance de canaux physiques de contrôle descendant (pdcch) de groupes d'ensembles d'espaces de recherche (sssg)
US20240155606A1 (en) Enhanced multi-layer uplink transmission
WO2022155488A1 (fr) Mécanismes de saut de fréquence améliorés pour dispositifs à capacité réduite (redcap)
US20230269057A1 (en) Unified transmission configuration indicator (tci) framework for multi-transmission-reception point (trp) operation
US20240155503A1 (en) Spatial relationship and power control configuration for uplink transmissions
US20240163900A1 (en) Single-dci-based physical uplink shared channel (pusch) transmission scheduling
WO2022187051A1 (fr) Planification de répétition pusch à points d'émission-réception multiples (multi-trp) à l'aide d'informations de commande de liaison descendante (dci)
WO2022169716A1 (fr) Systèmes et procédés d'indication de formation de faisceau
WO2022174070A1 (fr) Mesures de performances pour applications d'informatique en périphérie
WO2022170214A1 (fr) Gestion de congestion pour accès direct à la mémoire à distance (rdma) dans des réseaux cellulaires de prochaine génération
WO2022155487A1 (fr) Indication d'un faisceau sur la base d'informations de commande de liaison descendante (dci) pour réseau cellulaire sans fil
US20240155589A1 (en) Techniques for channel state information reference signal (csi-rs) transmission
US20240146454A1 (en) Enhanced mapping for control channel transmission based on polar code
US20230163916A1 (en) Techniques for ue positioning measurement in rrc_inactive or rrc_idle
US20240178939A1 (en) Techniques for multi-transmission-reception point (trp) based uplink channel transmission
WO2022174135A1 (fr) Techniques d'indication de schéma de modulation et de codage (mcs)
WO2022165139A1 (fr) Techniques pour une configuration, un déclenchement et une régulation de puissance de signal de référence de sondage (srs)
WO2023014910A1 (fr) Traitement de collision pour transmission de signal de référence de sondage (srs)
WO2022240862A1 (fr) Opérations sur faisceaux par défaut pour transmissions en liaison montante
WO2023069742A1 (fr) Perfectionnements de chaînes d'indicateur de configuration de transmission (tci) pour de nouveaux systèmes radio
WO2022178127A1 (fr) Mesures de performance pour la gestion de données et la commande de politique de transfert de données d'arrière-plan pour des systèmes de prochaine génération
WO2022204364A1 (fr) Transmissions de liaison montante non basées sur un livre de codes améliorées dans un réseau cellulaire sans fil

Legal Events

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

Ref document number: 22753480

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 202280025700.9

Country of ref document: CN

122 Ep: pct application non-entry in european phase

Ref document number: 22753480

Country of ref document: EP

Kind code of ref document: A1