KR20230171922A - Technologies for Modulation and Coding Scheme (MCS) Indication - Google Patents

Abstract

Various embodiments of the present specification provide techniques for designing a modulation and coding scheme (MCS) table in a wireless cellular system. The MCS table can be optimized for two multiple input, multiple output (MIMO) layer transmission, for example, without MIMO layer adaptation. Other embodiments may be described and claimed.

Description

Technologies for Modulation and Coding Scheme (MCS) Indication

<Cross-reference to related applications>

This application is related to U.S. Provisional Patent Application No. 63/149,529, filed on February 15, 2021; and U.S. Provisional Patent Application No. 63/155,243, filed March 1, 2021.

<Technology field>

Various embodiments may relate to the field of wireless communications generally. For example, some embodiments may involve a modulation and coding scheme (MCS) indication.

5G New Radio (NR) supports dynamic adaptation of transmission parameters to actual link conditions. More specifically, depending on the channel state information (CSI), the next-generation Node B (gNB) can use multiple input, multiple output (MIMO) layers for physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission. The optimal number and modulation and coding scheme (MCS) can be indicated to the user equipment (UE).

Embodiments may be easily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals indicate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the drawings of the accompanying drawings.
1 illustrates the spectral efficiency provided by the modulation and coding scheme tables described herein, according to various embodiments.
Figure 2 illustrates the spectral efficiencies associated with the MCS table in Table 5, according to various embodiments.
Figure 3 illustrates the spectral efficiencies associated with the MCS table in Table 6, according to various embodiments.
Figure 4 illustrates spectral efficiencies associated with the MCS table in Table 7, according to various embodiments.
Figure 5 illustrates spectral efficiencies associated with the MCS table in Table 8, according to various embodiments.
Figure 6 illustrates spectral efficiencies associated with the MCS table in Table 9, according to various embodiments.
Figure 7 illustrates spectral efficiency versus SNR with uniform quantization of the spectral efficiency range, according to various embodiments.
8 schematically illustrates a wireless network according to various embodiments.
9 schematically illustrates components of a wireless network according to various embodiments.
10 illustrates some example methods that can 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 block diagram illustrating components, according to embodiments.
11 illustrates a process in a user equipment (UE) according to various embodiments.
12 illustrates a process of a next-generation Node B (gNB), according to various embodiments.

The detailed description below refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify identical or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as specific structure, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art upon reading this disclosure that various aspects of the various embodiments may be practiced in other instances that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

Various embodiments herein provide techniques for modulation and coding scheme (MCS) table design assuming only two multiple input, multiple output (MIMO) layer transmission. In embodiments, the MCS table may be for transmission of a Physical Downlink Shared Channel (PDSCH) and/or a Physical Uplink Shared Channel (PUSCH) using two MIMO layers without MIMO layer adaptation. For example, PDSCH and/or PUSCH can be transmitted in sub-THz or THz channels and MIMO layer adaptation is not required.

As discussed above, 5G New Radio (NR) supports dynamic adaptation of transmission parameters to actual link conditions. More specifically, depending on the channel state information (CSI), the next-generation Node B (gNB) can indicate to the user equipment (UE) the optimal number of MIMO layers and modulation and coding scheme (MCS) for PDSCH or PUSCH transmission. there is.

The modulation order and target coding rate are provided to the UE using the MCS index. The MCS index is indicated to the UE by downlink control information (DCI) or radio resource control (RRC) (in case of configured acknowledge transmission) signaling. The MCS index refers to a row in the MCS table configured for the UE using RRC signaling. This includes the set of supported MCS indices and associated modulation order, quantized code rate, and spectral efficiency. Examples of MCS Table 1 (supporting modulation orders up to 64QAM) and MCS Table 2 (supporting modulation orders up to 256QAM) defined in 3GPP Technical Standard (TS) 38.214 v16.4.0 (“TS 38.214”) are provided below. do.

The number of MIMO layers provides information about the number of spatial data streams that can be transmitted. This may be indicated implicitly or explicitly (e.g., via the demodulation reference signal (DM-RS) antenna port field).

Based on the number of MCS and MIMO layers indicated, the UE determines the transport block size (TBS) for PUSCH or PDSCH transmission based on the four-step procedure described in TS 38.214.

It should be noted that for 6G systems operating in sub-THz or THz bands, the most common propagation condition between transmit (Tx) and receive (Rx) is line-of-sight (LOS) (or LOS-like). In these channels, the mutual interference between the two polarizations is easier to cancel out, allowing two MIMO layers transmission to be more efficient than a single MIMO layer in most cases. Therefore, link adaptation to the number of MIMO layers is not required. The current design of the MCS table is optimized assuming transmission with one or multiple MIMO layers.

The current MCS table is not optimized assuming transmission using only two MIMO layers.

Due to the characteristics of sub-THz or THz channels, MIMO layer adaptation is not required for PDSCH and PUSCH transmission. Various embodiments herein provide MCS table designs that assume only two MIMO layer transmission.

In a first embodiment, the MCS table for two MIMO layers can be constructed using the following procedure:

· Determine a reference set of spectral efficiencies using the reference MCS table for one and two MIMO layers. The reference MCS table may be MCS Table 1 or 2 from TS 38.214 (e.g., as presented above).

· The supported spectral efficiencies for the improved MCS table are obtained by aggregating the two sets of spectral efficiencies.

o The first set has a total spectral efficiency (across two MIMO layers) equal to the total spectral efficiency of a reference MCS table with two MIMO layers (e.g. MCS Table 1 or MCS Table 2 from TS 38.214) .

- The corresponding spectral efficiency from the improved MCS table is associated with the same modulation orders as for the corresponding MCS from the reference MCS table.

o The second set has a total spectral efficiency (across two MIMO layers) equal to the spectral efficiency of a reference MCS table with one MIMO layer (e.g. MCS Table 1 or MCS Table 2 from TS 38.214).

- Spectral efficiency is not included in the second set if the difference with any spectral efficiency from the first set is less than a predetermined threshold, the threshold may be an absolute or relative value.

- The spectral efficiency for the improved MCS table is associated with the same modulation order as for the corresponding MCS from the reference MCS table.

The first set of spectral efficiencies may correspond to improved MCS table rows whose modulation and code rate are reused from some rows of the reference MCS table.

The second set of spectral efficiencies is in the new improved MCS table rows where the modulation and code rate are selected to reproduce the spectral efficiency (SE) of the reference MCS table with an unsupported number of MIMO layers (e.g., rank 1). We can respond.

An example of the first embodiment is illustrated in Table 1, where the entries from the first set have indices 3-5, 7-8, 10-11, 13-18, 20-21, 23-25, 27-37. While corresponding to the MCS, the entries from the second set are MCS indices 0-2, 6, 9, 12, 19, 22, 26. MCS indices from the reference MCS table are provided within parentheses in the I _MCS column for the first set.

In a second embodiment, an improved MCS table for two MIMO layer transmission can be constructed using the following procedure:

· The spectral efficiencies for the improved MCS tables are obtained by aggregating the two sets of spectral efficiencies.

· The first set has total spectral efficiencies (across two layers) equal to the spectral efficiency of a reference MCS table with a single MIMO layer (e.g. MCS Table 1 or MCS Table 2).

o The corresponding spectral efficiency from the improved MCS table is associated with the same modulation orders as for the corresponding MCS from the reference MCS table.

· The second set has total spectral efficiencies (across the two layers) equal to the spectral efficiencies of a reference MCS table with two MIMO layers (e.g., MCS Table 1 or MCS Table 2), and It has spectral efficiencies higher than the maximum spectral efficiency.

o The corresponding spectral efficiency from the improved MCS table is associated with the same modulation orders as for the corresponding MCS from the reference MCS table.

The first set of spectral efficiencies may correspond to new improved MCS table rows where the modulation and code rate are selected to reproduce the spectral efficiency of a reference MCS table with an unsupported number of MIMO layers (e.g., rank 1). .

The second set of spectral efficiencies may correspond to improved MCS table rows whose modulation and code rate are reused from some rows of the reference MCS table.

An example of the second embodiment is illustrated in Table 2, where the entries from the first set are MCS with indices 0-27, while the entries from the second set are MCS indices 28-37. For MCS with MCS indices 28 to 37, indices from the reference MCS table are provided in parentheses.

In a third embodiment, the improved MCS table includes all spectral efficiencies supported by the reference MCS table for one and two MIMO layers with the same modulation orders. The improved MCS table is used for two MIMO layer transmission.

An example of the total spectral efficiencies supported by MCS tables constructed from the reference MCS table using Examples 1-3 is illustrated in Figure 1 (rows 3, 4). An example of the total spectral efficiencies supported by the reference MCS table is shown for reference (rows 1, 2).

In a fourth embodiment, the improved MCS table can also support pi/2 BPSK and 256QAM modulation. In particular, spectral efficiencies for MCS where the QPSK modulation order and coding rate are less than a predetermined value (eg, 1/5) can also be supported by an improved MCS table with pi/2 BPSK modulation. Similarly, additional spectral efficiency can be supported by MCS with 256QAM modulation order. The associated spectral efficiency figures for the improved MCS table can be determined by reference MCS Table 2. Examples of MCS tables supporting pi/2 BPSK, QSPK, 16QAM, 64QAM, and 256QAM modulation designed according to the fourth embodiment are shown in Table 3, and in the improved MCS table, pi/2 BPSK entries are 0-3. 256QAM entries have an MCS index of 40-47. It should be noted that MCS with pi/BPSK modulation provides the same spectral efficiency as specific MCS with QPSK modulation. In another embodiment, to reduce overhead, corresponding QPSK entries may be removed to reduce MCS indication overhead.

Another example of the fourth embodiment is illustrated in Table 4 supporting pi/2 BPSK, QSPK, 16QAM, 64QAM and 256QAM modulation. In the improved MCS table, MCS supporting pi/2 BPSK entries have an MCS index of 0-3 and 256QAM entries have an MCS index of 42-49.

In a fifth embodiment, the MCS table for two MIMO layer transmission can be constructed by selecting target spectral efficiency and modulation order to provide:

- a substantially uniform grid of target SNR (in dB) corresponding to the target BLER (e.g. 10%) of the corresponding MCS when used with a particular channel coding scheme;

- the maximum and minimum SNRs for the MCS are approximately equal to the SNRs of the MCS in the reference MCS table - the reference MCS table is MCS Table 1 and/or MCS Table 2 defined in TS 38.214 for 1 and 2 MIMO layers -;

- Code rate and modulation combination of the corresponding MCS that minimizes BLER when used with a specific channel coding scheme;

- Number of rows required to keep the DCI MCS field bitwidth below a predefined value; and/or

- SNR grid steps providing seamless link adaptation capabilities.

A first example of the fifth embodiment is provided in Table 5, where 29 entries were assumed to be available for explicit MCS indication. An additional three entries can be used to support 256QAM modulation or implicit MCS indication for adaptive HARQ retransmission.

An example of an MCS table design with spectral efficiencies that provide nearly uniform quantization in the SNR range is illustrated in Figure 2.

A second example of the fifth embodiment is provided in Table 6, where 32 entries were assumed to be available with modulation orders of QPSK, 16QAM, 64QAM and 256QAM used to quantize the corresponding spectral efficiency range. In another example of this embodiment, certain MCS entries associated with a QPSK modulation and coding rate below the threshold (e.g., a code rate of 1/5) are replaced with a pi/2 BPSK modulation order with a coding rate two times higher. It can be. Replacing QPSK entries with pi/2 BPSK entries can be fixed in the specification or configured by higher layers.

An example of an MCS table design with spectral efficiencies that provide nearly uniform quantization in the SNR range is illustrated in Figure 3.

A third example of the fifth embodiment is provided in Table 7, where 64 entries are assumed to be available, and modulation orders of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency ranges. . According to a third example, some MCS entries associated with QPSK modulation and a coding rate below the threshold (e.g., a code rate of 1/5) are substantially similar/identical to MCS entries with pi/2 BPSK modulation. It has spectral efficiency. Additionally, the maximum spectral efficiency of a particular modulation has a similar/same value as the minimum spectral efficiency of the next modulation order.

An example of an MCS table design with spectral efficiencies that provide nearly uniform quantization in the SNR range is illustrated in Figure 4.

A fourth example of the fifth embodiment is provided in Table 8, where 64 entries are assumed to be available, and modulation orders of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency ranges. . The spectral efficiency range extends to lower values (about 4 times lower than the lowest spectral efficiency supported in the third example of embodiment, Table 7).

An example of an MCS table design with spectral efficiencies that provide nearly uniform quantization in the SNR range is illustrated in Figure 5.

A fifth example of the fifth embodiment is provided in Table 9, where 64 entries are assumed to be available, and modulation orders of pi/2 BPSK, QPSK, 16QAM, 64QAM and 256QAM are used to quantize the corresponding spectral efficiency ranges. . This example reduces the quantization step between subsequent entries, while maintaining the same spectral efficiency range as in the third example of embodiment (Table 7).

An example of an MCS table design with spectral efficiencies that provide nearly uniform quantization in the SNR range is illustrated in Figure 6.

In the sixth embodiment, the approach taken in the fifth embodiment is reused. However, instead of a uniform grid of target SNR values (in dB) with a fixed SNR grid step, a uniform grid of given spectral efficiencies (SEs) is used. That is, in the sixth embodiment, unlike the target SNR range, the SE range is uniformly quantized. This approach is schematically depicted in Figure 7.

Systems and Implementations

8-10 illustrate various systems, devices, and components that can implement aspects of the disclosed embodiments.

Figure 8 illustrates a network 800 according to various embodiments. Network 800 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

Network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with RAN 804 via an over-the-air connection. UE 802 may be communicatively coupled to RAN 804 by a Uu interface. UE 802 is a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, and instrument cluster. ), head-up display device, onboard diagnostic device, dashboard mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system , sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc., but are not limited to these.

In some embodiments, network 800 may include a plurality of UEs directly coupled to each other through a sidelink interface. UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, UE 802 may additionally communicate with AP 806 via an over-the-air connection. AP 806 may manage the WLAN connection, which may serve to offload some/all network traffic from RAN 804. The connection between UE 802 and AP 806 may conform to any IEEE 802.11 protocol, and AP 806 may be a wireless fidelity (Wi-Fi®) router. In some embodiments, UE 802, RAN 804, and AP 806 may utilize cellular-WLAN aggregation (e.g., 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.

RAN 804 may include one or more access nodes, such as AN 808. AN 808 may terminate air-interface protocols for UE 802 by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 808 may enable data/voice connectivity between CN 820 and UE 802. In some embodiments, AN 808 may be implemented as one or more software entities running on server computers on a separate device or as part of a virtual network, which may be referred to, for example, as a CRAN or a pool of virtual baseband units. there is. AN 808 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 808 may be a macrocell base station or a low-power base station to provide femtocells, picocells or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. .

In embodiments where RAN 804 includes multiple ANs, these may be coupled to each other via an X2 interface (if RAN 804 is an LTE RAN) or an Xn interface (if RAN 804 is a 5G RAN). You can. X2/Xn interfaces, which in some embodiments may be separate control/user plane interfaces, allow ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. It is permissible.

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. UE 802 may be simultaneously connected to multiple cells provided by the same or different ANs of RAN 804. For example, UE 802 and RAN 804 may use carrier aggregation to allow UE 802 to connect with multiple component carriers corresponding to a Pcell or Scell, respectively. In dual connectivity scenarios, the first AN may be a master node providing MCG, and the second AN may be a secondary node providing SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

RAN 804 may provide air interface over licensed or unlicensed spectrum. To operate in unlicensed spectrum, nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing unlicensed spectrum, nodes may perform medium/carrier-sensing operations based, for example, on a listen-before-speak (LBT) protocol.

In V2X scenarios, UE 802 or AN 808 may be or act as an RSU, which may refer to any transport infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or stationary (or relative stationary) UE. The RSU is implemented in or by: where the UE may be referred to as a “UE-type RSU”; Where an eNB may be referred to as an “eNB-type RSU”; Where a gNB may be referred to as a “gNB-type RSU”; etc. In one example, an RSU is a computing device coupled to a radio frequency circuit located at the roadside that provides connectivity support for passing vehicle UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, as well as applications/software for sensing and controlling ongoing vehicular and pedestrian traffic. RSU can provide ultra-low latency communications required for high-speed events such as collision avoidance, traffic alerts, etc. Additionally or alternatively, the RSU may provide other cellular/WLAN communication services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a traffic signaling controller or a network interface controller to provide a wired connection (e.g., Ethernet) to a backhaul network.

In some embodiments, RAN 804 may be an LTE RAN 810 with eNBs, e.g., eNB 812. LTE RAN 810 may provide an LTE air interface with the following characteristics: SCS at 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; Turbo Code for data and TBCC for control; etc. The LTE air interface includes CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and cell search and initial acquisition for coherent demodulation/detection at the UE, channel quality measurements, and CRS for channel estimation. The LTE air interface can operate in sub-6 GHz bands.

In some embodiments, RAN 804 may be NG-RAN 814 with gNBs, e.g., gNB 816, or ng-eNBs, e.g., ng-eNB 818. . gNB 816 can connect with 5G-capable UEs using a 5G NR interface. gNB 816 may connect with the 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 can also connect with the 5G core through the NG interface, but can also connect with the UE through the LTE air interface. gNB 816 and ng-eNB 818 can be connected to each other through the Xn interface.

In some embodiments, the NG interface has two parts: an NG user plane (NG-U) interface (e.g., N3) that carries traffic data between nodes in NG-RAN 814 and UPF 848 interface), and an NG control plane (NG-C) interface (eg, N2 interface), which is a signaling interface between the nodes of the NG-RAN 814 and the AMF 844.

NG-RAN 814 can 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. 5G-NR air interface may not use CRS, PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; And a tracking reference signal for time tracking can be used. The 5G-NR air interface may operate in the FR1 bands, including bands below 6 GHz, or the FR2 bands, including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of the downlink resource grid including PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of SCS. For example, UE 802 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 802, the SCS of the transmission is also changed. Another use case example of BWP involves power saving. In particular, multiple BWPs may be configured for the UE 802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios. A BWP containing fewer PRBs can be used for data transmission with a small traffic load while allowing power savings at the UE 802 and in some cases at the gNB 816. BWP containing a larger number of PRBs can be used in scenarios with higher traffic load.

RAN 804 is communicatively coupled to CN 820, which includes network elements to provide various functions supporting data and communication services to customers/subscribers (e.g., users of UE 802). It rings. Components of CN 820 may be implemented on one physical node or on separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by network elements of CN 820 with physical computing/storage resources such as servers, switches, etc. . A logical instantiation of a CN 820 may be referred to as a network slice, and a logical instantiation of a portion of a CN 820 may be referred to as a network sub-slice.

In some embodiments, CN 820 may be an LTE CN 822, which may also be referred to as EPC. LTE CN 822 has MME 824, SGW 826, SGSN 828, HSS 830, and PGW 832 coupled to each other via interfaces (or “reference points”) as shown. , and PCRF 834. The functions of the elements of the LTE CN 822 can be briefly introduced as follows.

The MME 824 may implement mobility management functions to track the current location of the UE 802 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

SGW 826 may terminate the S1 interface towards the RAN and route data packets between the RAN and LTE CN 822. SGW 826 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

SGSN 828 may track the location of UE 802 and perform security functions and access control. Additionally, SGSN 828 provides inter-EPC node signaling for mobility between different RAT networks; Selection of PDN and S-GW specified by MME 824; MME selection for handovers; etc. can be performed. The S3 reference point between MME 824 and SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

HSS 830 may include a database for network users, including subscription-related information to support handling of communication sessions of network entities. HSS 830 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependency, etc. The S6a reference point between HSS 830 and MME 824 may enable transmission of subscription and authentication data to authenticate/authorize user access to LTE CN 820.

PGW 832 may terminate an SGi interface towards a data network (DN) 836 , which may include an application/content server 838 . PGW 832 may route data packets between LTE CN 822 and data network 836. PGW 832 may be coupled with SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 832 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. Additionally, the SGi reference point between PGW 832 and data network 836 may be an operator external public, private PDN, or an intra-operator packet data network, for example, for provisioning IMS services. PGW 832 may be coupled with PCRF 834 through a Gx reference point.

PCRF (834) is a policy and charging control element of LTE CN (822). PCRF 834 may be communicatively coupled to app/content server 838 to determine appropriate QoS and charging parameters for service flows. PCRF 832 may provision the associated rules (via the Gx reference point) to the PCEF with the appropriate TFT and QCI.

In some embodiments, CN 820 may be 5GC 840. 5GC 840 has AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, coupled to each other via interfaces (or “reference points”) as shown. It may include NEF (852), NRF (854), PCF (856), UDM (858), and AF (860). The functions of the elements of 5GC (840) can be briefly introduced as follows.

AUSF 842 may store data for authentication of UE 802 and handle authentication-related functionality. AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 840 via reference points as shown, AUSF 842 may represent a Nausf service based interface.

AMF 844 may allow other functions of 5GC 840 to communicate with UE 802 and RAN 804 and subscribe to notifications about mobility events for UE 802. AMF 844 may be responsible for registration management (e.g., UE 802 registration), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 844 provides transport for SM messages between UE 802 and SMF 846 and may act as a transparent proxy for routing SM messages. AMF 844 may also provide transport for SMS messages between UE 802 and SMSF. AMF 844 may interact with AUSF 842 and UE 802 to perform various security anchor and context management functions. Additionally, AMF 844 may be a termination point of a RAN CP interface, which may be or include an N2 reference point between RAN 804 and AMF 844; AMF 844 may be an termination point for NAS (N1) signaling and may perform NAS encryption and integrity protection. AMF 844 may also support NAS signaling with UE 802 via the N3 IWF interface.

SMF 846 supports SM (e.g., session establishment, tunnel management between UPF 848 and AN 808); UE IP address allocation and management (including optional authorization); Selection and control of UP functions; Configuration of traffic steering in UPF 848 to route traffic to the appropriate destination; Termination of interfaces towards policy control functions; Controls some of the policy enforcement, charging, and QoS; legal intercept (SM events and interface to LI system); Termination of SM portions of NAS messages; Downlink data notification; Initiation of AN specific SM information transmitted via N2 to AN 808 via AMF 844; and may be responsible for determining the SSC mode of the session. SM may refer to management of a PDU session, and 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.

UPF 848 is an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnect to data network 836, and a branch to support multi-homed PDU sessions. It can act as a branching point. UPF 848 also performs packet routing and forwarding, performs packet inspection, enforces the user plane portion of policy rules, legitimately intercepts packets (UP collection), performs traffic usage reporting, and user plane Performs QoS handling (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), and performs QoS handling on the uplink and downlink. Transport level packet marking can be performed, downlink packet buffering, and downlink data notification triggering can be performed. UPF 848 may include an uplink classifier to assist in routing traffic flows to the data network.

NSSF 850 may select a set of network slice instances serving UE 802. NSSF 850 may also determine mappings to allowed NSSAIs and subscribed S-NSSAIs, if necessary. NSSF 850 may also determine the set of AMFs, or list of candidate AMFs, to be used to serve UE 802 based on appropriate configuration and possibly by querying NRF 854. 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 in the AMF. NSSF 850 may interact with AMF 844 via N22 reference points and communicate with other NSSFs in the visited network via N31 reference points (not shown). Additionally, NSSF 850 may represent the Nnssf service-based interface.

NEF 852 provides services and capabilities provided by 3GPP network functions for third parties, internal exposure/re-exposure, AFs (e.g., AF 860), edge computing or fog computing systems, etc. can be safely exposed. In these embodiments, NEF 852 may authenticate, authorize, or throttle AFs. NEF 852 may also transform information exchanged with AF 860 and with internal network functions. For example, NEF 852 can convert between AF-Service-Identifier and internal 5GC information. NEF 852 may also receive information from other NFs based on their exposed capabilities. This information may be stored in NEF 852 as structured data, or in data storage NF using standardized interfaces. The stored information can then be re-exposed by NEF 852 to other NFs and AFs, or used for other purposes, such as analytics. Additionally, NEF 852 may represent an Nnef service-based interface.

The NRF 854 supports service discovery functions, receives NF discovery requests from NF instances, and provides information on discovered NF instances to NF instances. NRF 854 also maintains information about available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” etc. may refer to the creation of an instance, and “instance” may refer to, for example, a creation of an instance of program code. It can refer to specific occurrences of an object that may occur during execution. Additionally, NRF 854 may represent an Nnrf service-based interface.

PCF 856 may provide and enforce policy rules to control plane functions and may also support an integrated policy framework for controlling network behavior. PCF 856 may also implement a front end to access subscription information related to policy decisions in the UDR of UDM 858. In addition to communicating functions via reference points as shown, PCF 856 represents the Npcf service based interface.

UDM 858 may handle subscription-related information to support handling of network entities of communication sessions and may store subscription data of UE 802. For example, subscription data may be communicated via the N8 reference point between UDM 858 and AMF 844. UDM 858 may include two parts, an application front end and a UDR. UDR may be configured to include subscription data and policy data for UDM 858 and PCF 856, and/or structured data for exposure and application data for NEF 852 (PFDs for application detection, multiple UEs ( 802), including application request information, can be stored. UDM 858, PCF 856, and NEF 852 access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and receive notification of related data changes in the UDR. and a Nudr service-based interface may be represented by UDR 221 to allow subscribing. UDM may include UDM-FE, which is responsible for processing credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. UDM-FE accesses subscription information stored in UDR and performs authentication credential processing, user identity handling, access authorization, registration/portability management, and subscription management. In addition to communicating with other NFs via reference points as shown, UDM 858 may represent a Nudm service based interface.

AF 860 may provide application influence on traffic routing, provide access to NEF, and interact with policy frameworks for policy control.

In some embodiments, 5GC 840 may enable edge computing by selecting operator/third-party services to be geographically close to the point where UE 802 attaches to the network. This can reduce network load and latency. To provide edge computing implementations, 5GC 840 may select a UPF 848 that is close to the UE 802 and perform traffic steering from UPF 848 to the data network 836 via the N6 interface. This may be based on UE subscription data, UE location, and information provided by AF 860. In this way, AF 860 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 860 is considered a trusted entity, the network operator may allow AF 860 to interact directly with relevant NFs. Additionally, AF 860 may represent a Naf service-based interface.

Data network 836 may represent, for example, various network operator services, Internet access, or third party services that may be provided by one or more servers, including application/content server 838.

9 schematically illustrates a wireless network 900 according to various embodiments. Wireless network 900 may include UE 902 in wireless communication with AN 904. UE 902 and AN 904 may be similar and substantially interchangeable with similarly named components described elsewhere herein.

UE 902 may be communicatively coupled with AN 904 via connection 906 . Connection 906 is illustrated as an air interface enabling communication coupling, which may be consistent with cellular communication protocols such as mmWave or the LTE protocol or 5G NR protocol operating at frequencies below 6 GHz.

UE 902 may include a host platform 908 coupled with a modem platform 910. Host platform 908 may include application processing circuitry 912 that may be coupled with protocol processing circuitry 914 of modem platform 910. Application processing circuitry 912 may execute various applications for UE 902 that source/sink application data. 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 (eg, UDP) and Internet (eg, IP) operations.

Protocol processing circuitry 914 may implement one or more of the layer operations to facilitate transmission or reception of data over connection 906. Layer operations implemented by protocol processing circuitry 914 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

Modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations “beneath” the layer operations performed by protocol processing circuitry 914 in a network protocol stack. These operations include, for example, HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/demapping, modulation symbol mapping, received symbol/bit metric determination, space-time, space-frequency or spatial coding. Multi-antenna port precoding/decoding, which may include one or more of: reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and one of other related functions. It may include PHY operations including the above.

The modem platform 910 further includes a RF front end (RFFE) 924 that may include or be connected to transmit circuitry 918, receive circuitry 920, RF circuitry 922, and one or more antenna panels 926. It can be included. Briefly, transmit circuitry 918 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; Receive circuitry 920 may include an analog-to-digital converter, mixer, IF components, etc.; RF circuitry 922 may include low noise amplifier, power amplifier, power tracking components, etc.; RFFE 924 may include filters (e.g., surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. Selection and arrangement of components of transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panels 926 (generally referred to as “transmit/receive components”) may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, for example, in mmWave or frequencies below 6 gHz, etc. In some embodiments, transmit/receive components may be arranged in multiple parallel transmit/receive chains, placed on the same or different chips/modules, etc.

In some embodiments, protocol processing circuitry 914 may include one or more instances of control circuitry (not shown) to provide control functions for transmit/receive components.

UE reception may be established by and through antenna panels 926, RFFE 924, RF circuitry 922, receive circuitry 920, digital baseband circuitry 916, and protocol processing circuitry 914. there is. In some embodiments, antenna panels 926 may receive a transmission from AN 904 by receive-beamforming signals received by a plurality of antennas/antenna elements of one or more antenna panels 926. You can.

UE transmission may be established by and through protocol processing circuitry 914, digital baseband circuitry 916, transmission circuitry 918, RF circuitry 922, RFFE 924, and antenna panels 926. there is. In some embodiments, the transmitting components of the UE 904 may apply a spatial filter to the data to be transmitted to form the transmit beam emitted by the antenna elements of the antenna panels 926.

Similar to UE 902, AN 904 may include a host platform 928 coupled with a modem platform 930. Host platform 928 may include application processing circuitry 932 coupled with protocol processing circuitry 934 of 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. Components of AN 904 may be similar and substantially interchangeable with similarly named components of UE 902. In addition to performing data transmission/reception as described above, components of AN 908 include RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. It can perform various logical functions.

10 illustrates some example methods that can 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 block diagram illustrating components, according to embodiments. Specifically, FIG. 10 shows a schematic 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. and each of these may be communicatively coupled via bus 1040 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may run to provide an execution environment for one or more network slices/sub-slices to utilize hardware resources 1000. You can.

Processors 1010 may include processor 1012 and processor 1014, for example. Processors 1010 may include, 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, It may be an ASIC, FPGA, radio-frequency integrated circuit (RFIC), other processor (including those discussed herein), or any suitable combination thereof.

Memory/storage devices 1020 may include main memory, disk storage, or any suitable combination thereof. Memory/storage devices 1020 include 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, and solid state memory. -Can include, but is not limited to, any type of volatile, non-volatile, or semi-volatile memory, such as state storage, etc.

Communication resources 1030 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1004 or one or more databases 1006 or other network elements over network 1008. May include devices. For example, 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 are software, programs, applications, applets, apps, etc. to cause at least any of processors 1010 to perform any one or more of the methodologies discussed herein. Or it may contain other executable code. Instructions 1050 may reside fully or partially within at least one of processors 1010 (e.g., within the processor's cache memory), memory/storage devices 1020, or any suitable combination thereof. You can. Additionally, any portion of instructions 1050 may be transmitted to hardware resources 1000 from any combination of peripheral devices 1004 or databases 1006. Accordingly, the memory of processors 1010, memory/storage devices 1020, peripheral devices 1004, and databases 1006 are examples of computer-readable and machine-readable media.

Exemplary Procedures

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s) of Figures 8-10, or some other figures herein, or portions thereof. Implementations or implementations may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. One such process 1100 is shown in FIG. 11. In some embodiments, process 1100 may be performed by the UE or a portion thereof. At 1102, process 1100 may include receiving a modulation and coding scheme (MCS) index. At 1104, process 1100 may further include determining the modulation order, code rate, and spectral efficiency for transmission based on the entry in the MCS table corresponding to the MCS index, where the MCS table determines the MIMO layer adaptation. It is about a fixed number of multiple-input multiple-output (MIMO) layers. For example, the fixed number could be 2 or another suitable number of MIMO layers. At 1106, the process may further include sending or receiving a transmission based on modulation order, code rate, and spectral efficiency.

Figure 12 illustrates another process 1200 according to various embodiments. Process 1200 may be performed by a gNB or a portion thereof. At 1202, process 1200 may include determining an entry in a modulation and coding scheme (MCS) table for transmission with a fixed number of multiple-input multiple-output (MIMO) layers without MIMO layer adaptation, where the entry is: Includes MCS index, modulation order, code rate, and spectral efficiency. For example, the fixed number could be 2 or another suitable number of MIMO layers. At 1204, process 1200 may further include transmitting the MCS index to a user equipment (UE). At 1206, process 1200 may further include transmitting or receiving a transmission based on modulation order, code rate, and spectral efficiency.

For one or more embodiments, at least one of the components presented 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 Examples section below. For example, a baseband circuit as described above with respect to one or more of the preceding figures may be configured to operate according to one or more of the examples set forth below. By way of another example, circuitry associated with a UE, base station, network element, etc., as described above with respect to one or more of the preceding figures, may be configured to operate according to one or more of the examples presented below in the Examples section.

examples

Example A1 may include one or more non-transitory computer readable media (NTCRM) storing instructions that, when executed, cause a user equipment (UE) to: receive a modulation and coding scheme (MCS) index; Based on the entries in the MCS table corresponding to the MCS index, determine the modulation order, code rate, and spectral efficiency for transmission, where the MCS table has a fixed number of multiple input multiple output (MIMO) layers without MIMO layer adaptation. It is about -; Send or receive transmissions based on the corresponding modulation order, code rate, and spectral efficiency.

Example A2 may include one or more NTCRMs of Example A1, wherein the MCS table includes a plurality of entries corresponding to respective MCS indices, where each modulation order is pi/2 binary phase-shift keying (BPSK), There is at least one entry each for Quadrature Phase-Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM.

Example A3 may include one or more NTCRMs from Example A2, and there are 64 entries in the MCS table.

Example A4 may include one or more NTCRMs of Example A1, wherein the MCS table includes a plurality of entries corresponding to each MCS index, and the entries in the MCS table are combined: corresponding when used with a particular channel coding scheme. a substantially uniform grid of target signal-to-noise ratios (SNRs) corresponding to a target block error rate (BLER) of the MCS or a substantially uniform grid of spectral efficiencies of the corresponding MCS; A combination of code rate and modulation order for corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and provides the number of entries required to maintain the bit width of the MCS field in downlink control information below a predefined value.

Example A5 may include one or more NTCRMs of Example A4, wherein the entries in the MCS table include the maximum or minimum SNR corresponding to the target BLER in the MCS table and the respective maximum or minimum SNR corresponding to the target BLER in the reference MCS table. are combined to further provide maximum and minimum SNRs corresponding to the target BLER for the MCSs such that the absolute value of the decibel difference between them is less than the uniform SNR grid step provided by the MCS table.

Example A6 may include one or more NTCRMs of Example A5, and the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 v16.4.0 for one or two MIMO layers.

Example A7 may include one or more NTCRMs of Example A3, where the entries in the MCS table are combined to provide additional SNR grid steps below the threshold.

Example A8 may include one or more NTCRMs from any of Examples A1 through A7, and the MCS table is as follows:

I _MCS is the MCS index, Q _m is the modulation order, R is the code rate, and spectral efficiency (SE) per layer is the spectral efficiency per MIMO layer.

Example A9 may include one or more NTCRMs of any one of examples A1 to A7, with the fixed number being 2.

Example A10 may include a device in a user equipment (UE), the device including a memory storing 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 associated modulation orders and total spectral efficiencies equal to the corresponding entries of the reference MCS table with two MIMO layers; and a second set of entries with associated modulation orders and total spectral efficiencies equal to the corresponding entries of the reference MCS table with one MIMO layer. The apparatus may further include a processor circuit coupled to the memory, the processor circuit configured to receive the MCS index; Based on the MCS index and MCS table, determine the modulation order, code rate, and spectral efficiency for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH); configured to encode the PUSCH or decode the PDSCH for transmission based on modulation order, code rate, and spectral efficiency.

Example A11 may include the apparatus of example A10, wherein the reference MCS table with one MIMO layer when the difference between the spectral efficiency of the entry and any entry from the first set of entries is less than a predetermined threshold. The entries are not included in the second set.

Example A12 may include the apparatus of Example A11, wherein the threshold is an absolute or relative value.

Example A13 may include the apparatus of example A10, wherein the second set of entries have respective modulation orders and code rates to reproduce the corresponding spectral efficiency of the reference MCS table with one MIMO layer.

Example A14 may include the apparatus of example A10, where the PDSCH or PUSCH is transmitted without MIMO layer adaptation.

Example A15 may include the device of any of Examples A10 through A14, and 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 the Next-Generation Node B (gNB) to perform a fixed number of multi-input multiplexing without MIMO layer adaptation. Determine an entry in a modulation and coding scheme (MCS) table for transmission with output (MIMO) layers, where the entry includes MCS index, modulation order, code rate, and spectral efficiency; transmit the MCS index to user equipment (UE); Send or receive transmissions based on modulation order, code rate, and spectral efficiency.

Example A17 may include one or more NTCRMs of Example A16, wherein the MCS table includes a plurality of entries corresponding to respective MCS indices, where each modulation order is pi/2 binary phase-shift keying (BPSK), There is at least one entry each for Quadrature Phase-Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM.

Example A18 may include one or more NTCRMs from Example A17, and there are 64 entries in the MCS table.

Example A19 may include one or more NTCRMs of Example A16, wherein the MCS table includes a plurality of entries corresponding to each MCS index, and the entries in the MCS table are combined: corresponding when used with a particular channel coding scheme. a substantially uniform grid of target signal-to-noise ratios (SNRs) corresponding to a target block error rate (BLER) of the MCS or a substantially uniform grid of spectral efficiencies of the corresponding MCS; A combination of code rate and modulation order for corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and provides the number of entries required to maintain the bit width of the MCS field in downlink control information below a predefined value.

Example A20 may include one or more NTCRMs of Example A19, wherein the entries in the MCS table include the maximum or minimum SNR corresponding to the target BLER in the MCS table and the respective maximum or minimum SNR corresponding to the target BLER in the reference MCS table. are combined to further provide maximum and minimum SNRs corresponding to the target BLER for the MCSs such that the absolute value of the decibel difference between them is less than the uniform SNR grid step provided by the MCS table.

Example A21 may include one or more NTCRMs of Example A20, and the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 v16.4.0 for one or two MIMO layers.

Example A22 may include one or more NTCRMs of Example A19, where the entries in the MCS table are combined to provide additional SNR grid steps below the threshold.

Example A23 may include one or more NTCRMs from any of Examples A16 through A22, and the MCS table is as follows:

I _MCS is the MCS index, Q _m is the modulation order, R is the code rate, and spectral efficiency (SE) per layer is the spectral efficiency per MIMO layer.

Example A24 may include one or more NTCRMs of any of examples A16 to A22, with the fixed number being 2.

Example B1 may include a method of improved MCS table construction, the method being

determining a reference set of spectral efficiencies supported by a reference MCS table with one and multiple MIMO layers; and

and defining a new MCS table supporting a significant number of reference spectral efficiencies with a fixed number of MIMO layers, some of the reference spectral efficiencies may be approximated by similar values from the improved MCS table.

Example B2 may include the method of Example B1 or some other example herein, wherein the multiple MIMO layers correspond to two MIMO layers.

Example B3 may include the method of Example B1 or some other example herein, with the fixed number of MIMO layers corresponding to two MIMO layers.

Example B4 may include the method of Example B1 or some other example herein, where the supported spectral efficiencies for the improved MCS table are obtained by aggregating the two sets of spectral efficiencies.

Example B5 may include the method of Example B4 or some other examples herein, wherein the first set is the total spectral efficiency of a reference MCS table (e.g., MCS Table 1 or MCS Table 2) with two MIMO layers. and a second set of spectral efficiencies of a reference MCS table (e.g., MCS Table 1 or MCS Table 2) with a total spectral efficiency (e.g., across two MIMO layers) equal to have the same total spectral efficiency (e.g., across two MIMO layers), and the spectral efficiency is not included in the second set if the difference with any spectral efficiency from the first set is less than a predetermined threshold; The threshold may be an absolute or relative value.

Example B6 may include the method of Example B4 or some other examples herein, wherein the first set is equal to the spectral efficiency of a reference MCS table (e.g., MCS Table 1 or MCS Table 2) with a single MIMO layer. have total spectral efficiencies (e.g., across two layers), and the second set is equal to the spectral efficiency of a reference MCS table (e.g., MCS Table 1 or MCS Table 2) with two MIMO layers (e.g. has total spectral efficiencies (e.g., across two tiers) and has spectral efficiencies that are higher than the maximum spectral efficiency from the first set.

Example B7 can include the method of Examples B5 or B6 or some other example herein, wherein the corresponding spectral efficiency from the improved MCS table is associated with the same modulation orders as for the corresponding MCS from the reference MCS table. do.

Example B8 can include the method of Example B1 or some other examples herein, wherein the improved MCS table provides all spectral efficiencies supported by the reference MCS table for one and two MIMO layers with the same modulation orders. includes them.

Example B9 may include the method of Examples B1 or B4 or some other example herein, wherein the MCS table also has QPSK modulation and a pi/2 Includes MCS with BPSK modulation.

Example B10 may include the system and method of Example B9 or some other examples herein, wherein the predetermined value of the code rate is 1/5.

Example B11 may include a method of improved MCS table construction, which method

Select target spectral efficiencies and modulation orders that provide a substantially uniform grid of target signal-to-noise ratio (SNR) for transmission with a fixed number of MIMO layers corresponding to a fixed block error rate (BLER) of the corresponding MCS. steps;

selecting target minimum and maximum spectral efficiencies supported by the MCS table; and

It includes selecting the SNR level of the uniform grid of the target SNR.

Example B12 may include a method of improved MCS table construction, which method

selecting target spectral efficiencies and modulation orders that provide a substantially uniform grid of spectral efficiencies for transmission with a fixed number of MIMO layers;

selecting target minimum and maximum spectral efficiencies supported by the MCS table; and

and selecting a spectral efficiency level of the uniform spectral efficiency grid.

Example B13 may include the method of Example B11 or some other examples herein, wherein the BLER of the corresponding MCS is measured using an LDPC channel coding scheme.

Example B14 may include the method of Examples B11 or B12 or some other example herein, wherein the minimum and maximum spectral efficiencies are selected to be approximately equal to the minimum and maximum spectral efficiencies of the reference MCS table, and the reference MCS table is 1 MCS Table 1 and/or MCS Table 2 defined in TS 38.214 for 2 and 2 MIMO layers.

Example B15 may include the method of Example B11 or Example B12 or some other example herein, wherein the minimum and maximum spectral efficiencies are specified such that the target maximum and minimum SNRs supported by the MCS table are the maximum and minimum SNRs of the reference MCS table. Chosen to be approximately identical, the reference MCS table is MCS Table 1 and/or MCS Table 2 defined in TS 38.214 for one and two MIMO layers.

Example B16 may include the method of Example B11 or some other examples herein, wherein the SNR grid steps are selected to achieve a predefined DCI MCS field bitwidth.

Example B17 may include the method of Example B12 or some other examples herein, where the SE grid steps are selected to achieve a predefined DCI MCS field bitwidth.

Example B18 may include the method of Example B11 or some other examples herein, and the MCS table is according to Table 5.

Example B19 may include the method of Example B11 or some other examples herein, and the MCS table is according to Table 6.

Example B20 may include the method of Example B11 or some other examples herein, and the MCS table is according to Table 7.

Example B21 may include the method of Examples B11 or B12 or some other example herein, wherein MCS entries supporting pi/2 BPSK provide similar or identical spectral efficiency as a subset of MCS entries supporting QPSK modulation. do.

Example B22 may include the method of Example B11 or some other examples herein, and the MCS table is according to Table 8.

Example B23 may include the method of Example B11 or some other example herein, and the MCS table is according to Table 9.

Example B24 may include the system and method of Examples B11 or B12 or some other examples herein, wherein the MCS entries supporting pi/2 BPSK have similar or identical spectral efficiency as the subset of MCS entries supporting QPSK modulation. to provide.

Example B25 may include a method, which method is

determining one or more parameters for transmission of a signal based on one or more of the MCS tables herein; and

and encoding or decoding the signal based on the one or more determined parameters.

Example B26 may include the method of Example B25 or some other examples herein, wherein one or more parameters are determined based on the MCS index.

Example B27 may include the method of Examples B25-B26 or some other examples herein, wherein the one or more parameters include transport block size, number of layers, and/or spectral efficiency.

Example Z01 includes an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples A1-A24, B1-B27, or any other method or process described herein. can do.

Example Z02 may cause an electronic device to, upon execution of instructions by one or more processors of the electronic device, perform the method described in or related to any of Examples A1 through A24, Examples B1 through B27, or the method described herein. and one or more non-transitory computer-readable media containing instructions to perform one or more elements of any other method or process.

Example Z03 includes logic, modules, or circuitry for performing one or more elements of the method described or related to any of Examples A1 through A24, B1 through B27, or any other method or process described herein. It may include a device including a.

Example Z04 may include a method, technique, or process described in or related to any of Examples A1-A24, B1-B27, or portions or portions thereof.

Example Z05 may include an apparatus, the 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 a method, technique, or process as described in or related to any of Examples 1 through 25 or portions thereof.

Example Z06 may include a signal described in or related to any of Examples A1 through A24, Examples B1 through B27, or portions or portions thereof.

Example Z07 includes a datagram, packet, frame, as described in or related to any of Examples A1 through A24, B1 through B27, or portions or portions thereof, or otherwise described in this disclosure. It may contain segments, protocol data units (PDUs), or messages.

Example Z08 includes a signal encoded with data as described in or related to Examples A1 through A24, Examples B1 through B27, or any portion or portions thereof, or otherwise described in this disclosure. It can be included.

Example Z09 is a datagram, packet, as described in or related to any of Examples A1 through A24, Examples B1 through B27, or portions or portions thereof, or otherwise described in this disclosure. , may include signals encoded as frames, segments, protocol data units (PDUs), or messages.

Example Z10 can include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors causes the one or more processors to perform any of Examples A1-A24, B1-B27. or to perform a method, technique, or process as described in or related to portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to To cause a method, technique, or process to be performed.

Example Z12 may include signals in a wireless network as presented and described herein.

Example Z13 may include a method of communication in a wireless network as presented and described herein.

Example Z14 may include a system for providing wireless communications as presented and described herein.

Example Z15 may include a device for providing wireless communications as presented and described herein.

Unless explicitly stated otherwise, any of the examples described above may be combined with any other example (or combination of examples). The foregoing description of one or more implementations provides examples and explanations, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

3GPP Third Generation Partnership Project

4G Fourth Generation

5G Fifth Generation

5GC 5G Core network

AC Application Client

ACK Acknowledgment

ACID Application Client Identification

AF Application Function

A.M. Acknowledged Mode

AMBR Aggregate Maximum Bit Rate

AMF Access and Mobility Management Function

AN Access Network

ANR Automatic Neighbor Relation

AP Application Protocol, Antenna Port, Access Point

API Application Programming Interface

APNs Access Point Name

ARP Allocation and Retention Priority

ARQ Automatic Repeat Request

AS Access Stratum

ASP Application Service Provider

ASN.1 Abstract Syntax Notation One

AUSF Authentication Server Function

AWGN Additive White Gaussian Noise

BAP Backhaul Adaptation Protocol

BCH Broadcast Channel

BER Bit Error Ratio

BFD Beam Failure Detection

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BRAS Broadband Remote Access Server

BSS Business Support System

B.S. Base Station

BSR Buffer Status Report

BW Bandwidth

BWP Bandwidth Part

C-RNTIs Cell Radio Network Temporary Identity

CA Carrier Aggregation, Certification Authority

CAPEX Capital Expenditure

CBRA Contention Based Random Access

CC Component Carrier, Country Code, Cryptographic Checksum

CCA Clear Channel Assessment

CCE Control Channel Element

CCCH Common Control Channel

C.E. Coverage Enhancement

CDM Content Delivery Network

CDMA Code-Division Multiple Access

CFRA Contention Free Random Access

CG Cell Group

CGF Charging Gateway Function

CHF Charging Function

C.I. Cell Identity

CID Cell-ID (e.g., positioning method)

CIM Common Information Model

CIR Carrier to Interference Ratio

C.K. Cipher Key

CM Connection Management, Conditional Mandatory

CMAS Commercial Mobile Alert Service

CMD Command

CMS Cloud Management System

C.O. Conditional Optional

CoMP Coordinated Multi-Point

CORESET Control Resource Set

COTS Commercial Off-The-Shelf

CP Control Plane, Cyclic Prefix, Connection Point

CPD Connection Point Descriptor

CPE Customer Premise Equipment

CPICH Common Pilot Channel

CQI Channel Quality Indicator

CPU CSI processing unit, Central Processing Unit

C/R Command/Response field bit

CRAN Cloud Radio Access Network, Cloud RAN

CRB Common Resource Block

CRC Cyclic Redundancy Check

CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator

C-RNTIs Cell RNTI

C.S. Circuit Switched

CSAR Cloud Service Archive

CSI Channel-State Information

CSI-IM CSI Interference Measurement

CSI-RS CSI Reference Signal

CSI-RSRP CSI reference signal received power

CSI-RSRQ CSI reference signal received quality

CSI-SINR CSI signal-to-noise and interference ratio

CSMA Carrier Sense Multiple Access

CSMA/CA CSMA with collision avoidance

CSS Common Search Space, Cell-specific Search Space

CTF Charging Trigger Function

CTS Clear-to-Send

C.W. Codeword

CWS Contention Window Size

D2D Device-to-Device

D.C. Dual Connectivity, Direct Current

DCI Downlink Control Information

DF Deployment Flavor

DL Downlink

DMTF Distributed Management Task Force

DPDK Data Plane Development Kit

DM-RS, DMRS Demodulation Reference Signal

DN Data network

DNN Data Network Name

DNAI Data Network Access Identifier

D.R.B. Data Radio Bearer

DRS Discovery Reference Signal

DRX Discontinuous Reception

DSL Domain Specific Language, Digital Subscriber Line

DSLAM DSL Access Multiplexer

DwPTS Downlink Pilot Time Slot

E-LAN Ethernet Local Area Network

E2E End-to-End

ECCA extended clear channel assessment, extended CCA

ECCE Enhanced Control Channel Element, Enhanced CCE

ED Energy Detection

EDGE Enhanced Datarates for GSM Evolution

EAS Edge Application Server

EASID Edge Application Server Identification

ECS Edge Configuration Server

ECSP Edge Computing Service Provider

EDN Edge Data Network

EEC Edge Enabler Client

EECID Edge Enabler Client Identification

EES Edge Enabler Server

EESID Edge Enabler Server Identification

EHE Edge Hosting Environment

EGMF Exposure Governance Management Function

EGPRS Enhanced GPRS

EIR Equipment Identity Register

eLAA enhanced Licensed Assisted Access, enhanced LAA

EM Element Manager

eMBB Enhanced Mobile Broadband

EMS Element Management System

eNB evolved NodeB, E-UTRAN Node B

EN-DC E-UTRA-NR Dual Connectivity

EPC Evolved Packet Core

EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Cannel

EPRE Energy per resource element

EPS Evolved Packet System

EREG enhanced REG, enhanced resource element groups

ETSI European Telecommunications Standards Institute

ETWS Earthquake and Tsunami Warning System

eUICC embedded UICC, embedded universal integrated circuit card

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

EV2X Enhanced V2X

F1AP F1 Application Protocol

F1-C F1 Control plane interface

F1-U F1 User plane interface

FACCH Fast Associated Control CHannel

FACCH/F Fast Associated Control Channel/Full rate

FACCH/H Fast Associated Control Channel/Half rate

FACH Forward Access Channel

FAUSCH Fast Uplink Signaling Channel

FB Functional Block

FBI Feedback Information

FCC Federal Communications Commission

FCCH Frequency Correction CHannel

FDD Frequency Division Duplex

FDM Frequency Division Multiplex

FDMA Frequency Division Multiple Access

F.E. Front End

FEC Forward Error Correction

FFS For Further Study

FFT Fast Fourier Transformation

feLAA further enhanced Licensed Assisted Access, further enhanced LAA

F.N. Frame Number

FPGA Field-Programmable Gate Array

FR Frequency Range

FQDN Fully Qualified Domain Name

G-RNTI GERAN Radio Network Temporary Identity

GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

GGSN Gateway GPRS Support Node

GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System)

gNB Next Generation NodeB

gNB-CU gNB-centralized unit, Next Generation NodeB centralized unit

gNB-DU gNB-distributed unit, Next Generation NodeB distributed unit

GNSS Global Navigation Satellite System

GPRS General Packet Radio Service

GPSI Generic Public Subscription Identifier

GSM Global System for Mobile Communications, Groupe Special Mobile

GTP GPRS Tunneling Protocol

GTP-U GPRS Tunnelling Protocol for User Plane

GTS Go To Sleep Signal (WUS related)

GUMMEI Globally Unique MME Identifier

GUTI Globally Unique Temporary UE Identity

HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

HANDO Handover

HFN HyperFrame Number

HHO Hard Handover

HLR Home Location Register

H.N. Home Network

HO Handover

HPLMN Home Public Land Mobile Network

HSDPA High Speed Downlink Packet Access

HSN Hopping Sequence Number

HSPA High Speed Packet Access

HSS Home Subscriber Server

HSUPA High Speed Uplink Packet Access

HTTP Hyper Text Transfer Protocol

HTTPS Hyper Text Transfer Protocol Secure (https is SSL, i.e. http/1.1 over port 443)

I-Block Information Block

ICCID Integrated Circuit Card Identification

IAB Integrated Access and Backhaul

ICIC Inter-Cell Interference Coordination

ID Identity, identifier

IDFT Inverse Discrete Fourier Transform

I.E. Information element

IBE In-Band Emission

IEEE Institute of Electrical and Electronics Engineers

I.E.I. Information Element Identifier

IEIDL Information Element Identifier Data Length

IETF Internet Engineering Task Force

IF Infrastructure

IM Interference Measurement, Intermodulation, IP Multimedia

IMC IMS Credentials

IMEI International Mobile Equipment Identity

IMGI International mobile group identity

IMPI IP Multimedia Private Identity

IMPU IP Multimedia PUblic identity

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity

IoT Internet of Things

IP Internet Protocol

ipsec IP Security, Internet Protocol Security

IP-CAN IP-Connectivity Access Network

IP-M IP Multicast

IPv4 Internet Protocol Version 4

IPv6 Internet Protocol Version 6

IR Infrared

IS In Sync

IRP Integration Reference Point

ISDN Integrated Services Digital Network

ISIM IM Services Identity Module

ISO International Organization for Standardization

ISP Internet Service Provider

IWF Interworking-Function

I-WLAN Interworking WLAN

Constraint length of the convolutional code, USIM Individual key

kB Kilobyte (1000 bytes)

kbps kilo-bits per second

Kc Ciphering key

Ki Individual subscriber authentication key

KPIs Key Performance Indicator

KQI Key Quality Indicator

KSI Key Set Identifier

ksps kilo-symbols per second

KVM Kernel Virtual Machine

L1 Layer 1 (Physical Layer)

L1-RSRP Layer 1 reference signal received power

L2 Layer 2 (data link layer)

L3 Layer 3 (network layer)

LAA Licensed Assisted Access

LAN Local Area Network

LADN Local Area Data Network

LBT Listen Before Talk

LCM LifeCycle Management

LCR Low Chip Rate

LCS Location Services

LCID Logical Channel ID

L.I. Layer Indicator

LLC Logical Link Control, Low Layer Compatibility

LPLMN Local PLMN

LPP LTE Positioning Protocol

LSB Least Significant Bit

LTE Long Term Evolution

L.W.A. LTE-WLAN aggregation

LWIP LTE/WLAN Radio Level Integration with IPsec Tunnel

LTE Long Term Evolution

M2M Machine-to-Machine

MAC Medium Access Control (Protocol Layering Context)

MAC Message authentication code (security/encryption context)

MAC-A MAC used for authentication and key agreement (TSG T WG3 context)

MAC-I MAC used for data integrity of signaling messages (TSG T WG3 context)

MANO Management and Orchestration

MBMS Multimedia Broadcast and Multicast Service

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MCC Mobile Country Code

MCG Master Cell Group

MCOT Maximum Channel Occupancy Time

MCS Modulation and coding scheme

MDAF Management Data Analytics Function

MDAS Management Data Analytics Service

MDT Minimization of Drive Tests

M.E. Mobile Equipment

MeNB master eNB

MER Message Error Ratio

MGL Measurement Gap Length

MGRP Measurement Gap Repetition Period

MIB Master Information Block, Management Information Base

MIMO Multiple Input Multiple Output

MLC Mobile Location Center

MM Mobility Management

MME Mobility Management Entity

M.N. Master Node

MNO Mobile Network Operator

M.O. Measurement Object, Mobile Originated

MPBCH MTC Physical Broadcast CHannel

MPDCCH MTC Physical Downlink Control CHannel

MPDSCH MTC Physical Downlink Shared CHannel

MPRACH MTC Physical Random Access CHannel

MPUSCH MTC Physical Uplink Shared Channel

MPLS MultiProtocol Label Switching

M.S. Mobile Station

MSB Most Significant Bit

M.S.C. Mobile Switching Center

MSI Minimum System Information, MCH Scheduling Information

MSID Mobile Station Identifier

MSIN Mobile Station Identification Number

MSISDN Mobile Subscriber ISDN Number

MT Mobile Terminated (Mobile Termination)

MTC Machine-Type Communications

mmTC Massive MTC, Massive Machine-Type Communications

MU-MIMO Multi User MIMO

MWUS MTC wake-up signal, MTC WUS

NACK Negative Acknowledgment

NAI Network Access Identifier

NAS Non-Access Stratum, Non-Access Stratum layer

NCT Network Connectivity Topology

NC-JT Non-Coherent Joint Transmission

NEC Network Capability Exposure

NE-DC NR-E-UTRA Dual Connectivity

NEF Network Exposure Function

NF Network Function

NFP Network Forwarding Path

NFPD Network Forwarding Path Descriptor

NFV Network Functions Virtualization

NFVI NFV Infrastructure

NFVO NFV Orchestrator

NG Next Generation (Next Gen)

NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

NM Network Manager

NMS Network Management System

N-PoP Network Point of Presence

NMIB, N-MIB Narrowband MIB

NPBCH Narrowband Physical Broadcast CHannel

NPDCCH Narrowband Physical Downlink Control CHannel

NPDSCH Narrowband Physical Downlink Shared CHannel

NPRACH Narrowband Physical Random Access CHannel

NPUSCH Narrowband Physical Uplink Shared CHannel

NPSS Narrowband Primary Synchronization Signal

NSSS Narrowband Secondary Synchronization Signal

NR New Radio, Neighbor Relation

NRF NF Repository Function

NRS Narrowband Reference Signal

NS Network Service

NSA Non-Standalone operation mode

NSD Network Service Descriptor

NSR Network Service Record

NSSAI Network Slice Selection Assistance Information

S-NNSAI Single-NSSAI

NSSF Network Slice Selection Function

N.W. Network

NWUS Narrowband wake-up signal, Narrowband WUS

NZP Non-Zero Power

O&M Operation and Maintenance

ODU2 Optical channel Data Unit - type 2

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OOB Out-of-band

OOS Out of Sync

OPEX Operating Expenses

OSI Other System Information

OSS Operations Support System

OTA over-the-air

PAPR Peak-to-Average Power Ratio

PAR Peak to Average Ratio

PBCH Physical Broadcast Channel

PC Power Control, Personal Computer

PCC Primary Component Carrier, Primary CC

PCell Primary Cell

PCI Physical Cell ID, Physical Cell Identity

PCEF Policy and Charging Enforcement Function

PCF Policy Control Function

PCRF Policy Control and Charging Rules Function

PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDN Packet Data Network, Public Data Network

PDSCH Physical Downlink Shared Channel

PDU Protocol Data Unit

P.E.I. Permanent Equipment Identifiers

PFD Packet Flow Description

P-GW PDN Gateway

PHICH Physical hybrid-ARQ indicator channel

PHY Physical layer

PLMN Public Land Mobile Network

PIN Personal Identification Number

PM Performance Measurement

PMI Precoding Matrix Indicator

PNF Physical Network Function

PNFD Physical Network Function Descriptor

PNFR Physical Network Function Record

POC PTT over Cellular

PP, PTP Point-to-Point

PPP Point-to-Point Protocol

PRACH Physical RACH

PRB Physical resource block

PRG Physical resource block group

ProSe Proximity Services, Proximity-Based Service

PRS Positioning Reference Signal

PRR Packet Reception Radio

P.S. Packet Services

PSBCH Physical Sidelink Broadcast Channel

PSDCH Physical Sidelink Downlink Channel

PSCCH Physical Sidelink Control Channel

PSSCH Physical Sidelink Shared Channel

PSCell Primary SCell

P.S.S. Primary Synchronization Signal

PSTN Public Switched Telephone Network

PT-RS Phase-tracking reference signal

PTT Push-to-Talk

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

QAM Quadrature Amplitude Modulation

QCI QoS class of identifier

QCL Quasi co-location

QFI QoS Flow ID, QoS Flow Identifier

QoS Quality of Service

QPSK Quadrature (Quaternary) Phase Shift Keying

QZSS Quasi-Zenith Satellite System

RA-RNTI Random Access RNTI

RAB Radio Access Bearer, Random Access Burst

RACH Random Access Channel

RADIUS Radius (Remote Authentication Dial In User Service)

RAN Radio Access Network

RAND Random number (RANDom number) (used for authentication)

RAR Random Access Response

RAT Radio Access Technology

RAU Routing Area Update

RB Resource block, Radio Bearer

R.B.G. Resource block group

REG Resource Element Group

Rel Release

REQ REQuest

RF Radio Frequency

R.I. Rank Indicator

RIV Resource indicator value

R.L. Radio Link

R.L.C. Radio Link Control, Radio Link Control layer

R.L.C. AM RLC Acknowledged Mode

R.L.C. UM RLC Unacknowledged Mode

RLF Radio Link Failure

R.L.M. Radio Link Monitoring

RLM-RS Reference Signal for RLM

RM Registration Management

R.M.C. Reference Measurement Channel

RMSI Remaining MSI, Remaining Minimum System Information

R.N. Relay Node

RNC Radio Network Controller

RNL Radio Network Layer

RNTI Radio Network Temporary Identifier

ROHC RObust Header Compression

RRC Radio Resource Control, Radio Resource Control layer

RRM Radio Resource Management

R.S. Reference Signal

RSRP Reference Signal Received Power

RSRQ Reference Signal Received Quality

RSSI Received Signal Strength Indicator

RSU Road Side Unit

RSTD Reference Signal Time difference

RTP Real Time Protocol

RTS Ready-To-Send

RTT Round Trip Time

Rx Reception, Receiving, Receiver

S1AP S1 Application Protocol

S1-MME S1 for the control plane

S1-U S1 for the user plane

S-GW Serving Gateway

S-RNTI SRNC Radio Network Temporary Identity

S-TMSI SAE Temporary Mobile Station Identifier

SA Standalone operation mode

S.A.E. System Architecture Evolution

SAP Service Access Point

SAPD Service Access Point Descriptor

SAPI Service Access Point Identifier

SCC Secondary Component Carrier, Secondary CC

SCell Secondary Cell

SCEF Service Capability Exposure Function

SC-FDMA Single Carrier Frequency Division Multiple Access

SCG Secondary Cell Group

SCM Security Context Management

SCS Subcarrier Spacing

SCTP Stream Control Transmission Protocol

SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol layer

SDL Supplementary Downlink

SDNF Structured Data Storage Network Function

SDP Session Description Protocol

SDSF Structured Data Storage Function

SDU Service Data Unit

SEAF Security Anchor Function

SeNB Secondary eNB

SEPP Security Edge Protection Proxy

SFI Slot format indication

SFTD Space-Frequency Time Diversity, SFN and frame timing difference

SFN System Frame Number

SgNB Secondary gNB

SGSN Serving GPRS Support Node

S-GW Serving Gateway

SI System Information

SI-RNTI System Information RNTI (System Information RNTI)

SIB System Information Block

sim Subscriber Identity Module

SIP Session Initiated Protocol

SiP System in Package

SL Sidelink

SLAs Service Level Agreement

SM Session Management

SMF Session Management Function

sms Short Message Service

SMSF SMS Function

SMTC SSB-based Measurement Timing Configuration

S.N. Secondary Node, Sequence Number

SoC System on Chip

SON Self-Organizing Network

SpCell Special Cell

SP-CSI-RNTI Semi-Persistent CSI RNTI

SPS Semi-Persistent Scheduling

SQN Sequence number

S.R. Scheduling Request

S.R.B. Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSID Service Set Identifier

SS/PBCH block

SSBRI SS/PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator

S.S.C. Session and Service Continuity

SS-RSRP Synchronization Signal based Reference Signal Received Power

SS-RSRQ Synchronization Signal based Reference Signal Received Quality

SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio

SSS Secondary Synchronization Signal

SSSG Search Space Set Group

SSSIF Search Space Set Indicator

SST Slice/Service Types

SU-MIMO Single User MIMO

SUL Supplementary Uplink

TA Timing Advance, Tracking Area

TAC Tracking Area Code

TAG Timing Advance Group

TAI Tracking Area Identity

TAU Tracking Area Update

TB Transport Block

TBS Transport Block Size

TBD To Be Defined

TCI Transmission Configuration Indicator

TCP Transmission Communication Protocol

TDD Time Division Duplex

TDM Time Division Multiplexing

TDMA Time Division Multiple Access

T.E. Terminal Equipment

TEID Tunnel End Point Identifier

TFT Traffic Flow Template

TMSI Temporary Mobile Subscriber Identity

TNL Transport Network Layer

T.P.C. Transmit Power Control

TPMI Transmitted Precoding Matrix Indicator

TR Technical Report

T.R.P., TRxP Transmission Reception Point

TRS Tracking Reference Signal

TRx Transceiver

TS Technical Specifications, Technical Standard

T.T.I. Transmission Time Interval

Tx Transmission, Transmitting, Transmitter

U-RNTI UTRAN Radio Network Temporary Identity

UART Universal Asynchronous Receiver and Transmitter

UCI Uplink Control Information

UE User Equipment

UDM Unified Data Management

UDP User Datagram Protocol

UDSF Unstructured Data Storage Network Function

UICC Universal Integrated Circuit Card

UL Uplink

UM Unacknowledged Mode

UML Unified Modeling Language

UMTS Universal Mobile Telecommunications System

UP User Plane

UPF User Plane Function

URI Uniform Resource Identifier

URL Uniform Resource Locator

URLLC Ultra-Reliable and Low Latency

USB Universal Serial Bus

USIM Universal Subscriber Identity Module

U.S.S. UE-specific search space

UTRA UMTS Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

UwPTS Uplink Pilot Time Slot

V2I Vehicle-to-Infrastructure

V2P Vehicle-to-Pedestrian

V2V Vehicle-to-Vehicle

V2X Vehicle-to-everything

VIM Virtualized Infrastructure Manager

V.L. Virtual Link,

VLAN Virtual LAN, Virtual Local Area Network

VM Virtual Machine

VNFs Virtualized Network Function

VNFG VNF Forwarding Graph

VNFFGD VNF Forwarding Graph Descriptor

VNFM VNF Manager

VoIP Voice-over-IP, Voice-over-Internet Protocol

VPLMN Visited Public Land Mobile Network

VPN Virtual Private Network

VRB Virtual Resource Block

WiMAX WiMAX (Worldwide Interoperability for Microwave Access)

WLAN Wireless Local Area Network

WMAN Wireless Metropolitan Area Network

WPAN Wireless Personal Area Network

X2-C X2-Control plane

X2-U X2-User plane

XML eXtensible Markup Language

XRES EXPECTED USER RESponse

XOR Exclusive OR

Z.C. Zadoff-Chu

ZP Zero Power

Terms

For the purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

As used herein, the term "circuitry" refers to an electronic circuit, logic circuit, processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) configured to provide the described functionality; ASIC (Application Specific Integrated Circuit), FPD (field-programmable device) (e.g., FPGA (field-programmable gate array), PLD (programmable logic device), CPLD (complex PLD), HCPLD (high-capacity PLD), Refers to, is part of, or includes hardware components such as a structured ASIC (or programmable SoC), digital signal processors (DSPs), etc. In some embodiments, circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuit” may also refer to a combination of program code and one or more hardware elements (or a combination of circuits used in an electrical or electronic system) used to perform the function of the program code. In these embodiments, a combination of hardware elements and program code may be referred to as a particular type of circuit.

As used herein, the term "processor circuitry" refers to circuitry that sequentially and automatically performs a sequence of arithmetic or logical operations, or that is capable of recording, storing, and/or transmitting digital data. It is a part or includes it. Processing circuitry may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuit” refers 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 program code. , software modules, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as functional processes. The processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, etc. One or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous with, and may be referred to as, “processor circuitry.”

As used herein, the term “interface circuitry” refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuit” may refer to one or more hardware interfaces, such as a bus, I/O interface, peripheral component interface, network interface card, etc.

As used herein, the term “user equipment” or “UE” refers to a device with radio communication capabilities and may describe a remote user of network resources of a communications network. The term “user equipment” or “UE” means 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 (radio equipment). equipment), reconfigurable radio equipment, reconfigurable mobile device, etc., and may be referred to as such. The term “user equipment” or “UE” may also include any computing device or any type of wireless/wired device that includes a wireless communication interface.

As used herein, the term “network element” refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” is considered synonymous with networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc. may be and/or may be referred to as such.

As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled to each other. Additionally, the terms “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled to each other and configured to share computing and/or networking resources.

As used herein, the terms “appliance,” “computer appliance,” and the like refer to a computer device or computer with program code (e.g., software or firmware) specifically designed to provide specific computing resources. refers to the system. A “virtual appliance” is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

As used herein, the term “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, It refers to memory usage, storage, network, database and applications, workload units, etc. “Hardware resource” may refer to computing, storage, and/or network resources provided by physical hardware element(s). “Virtualized resource” may refer to computing, storage, and/or network resources provided to an application, device, system, etc. by a virtualization infrastructure. The term “network resource” or “communication resource” may refer to resources accessible by computer devices/systems through a communication network. The term “system resources” may refer to any kind of shared entities for providing services, and may include computing and/or network resources. System resources can be thought of as a set of coherent functions, network data objects or services accessible through a server, which reside on a single host or multiple hosts and are clearly identifiable. do.

As used herein, the term “channel” refers to any transmission medium, tangible or intangible, used to communicate data or data streams. The term “channel” means “communication channel”, “data communication channel”, “transmission channel”, “data transmission channel”, “access channel”, “data access channel”, “link”, “data link”, “carrier”. , “radio frequency carrier,” and/or any other similar term referring to the path or medium over which data is communicated may be synonymous with and/or equivalent thereto. Additionally, the term “link” as used herein refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

As used herein, the terms “instantiate”, “instantiation”, etc. refer to the creation of an instance. “Instance” also refers to a specific occurrence of an object that may occur, for example, during the execution of program code.

The terms “coupled,” “communicatively coupled,” along with their derivatives are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, or can mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, And/or it may mean that one or more other elements are coupled or connected between elements mentioned as being coupled to each other. The term “directly coupled” may mean that two or more elements are in direct contact with each other. The term “communicatively coupled” may mean that two or more elements can be contacted by communication, including via a wired or other interconnect connection, via a wireless communication channel or link, and the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to the individual content of an information element, or a data element containing the content.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to SS/PBCH block.

The term “Primary Cell” refers to an MCG cell operating at a primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

The term “Primary SCG Cell” refers to an SCG cell that performs random access when the UE performs reconfiguration with the Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell that provides additional radio resources over a special cell for a UE configured as a CA.

The term “Secondary Cell Group” refers to a subset of serving cells that include a PSCell and zero or more secondary cells for a UE configured as a DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED that is not configured with a CA/DC, and there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to a set of cells including the special cell(s) and all secondary cells for a UE of RRC_CONNECTED configured with CA/.

The term “Special Cell” refers to a PCell in an MCG or a PSCell in an SCG for DC operation; otherwise, the term “Special Cell” refers to a Pcell.

Claims (24)

One or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed, cause a user equipment (UE) to:
Receive a modulation and coding scheme (MCS) index;
Based on the entry in the MCS table corresponding to the MCS index, determine the modulation order, code rate, and spectral efficiency for transmission, wherein the MCS table provides a fixed number of multiple input multiple output (MIMO) signals without MIMO layer adaptation. It's about classes -; and
One or more NTCRMs to transmit or receive the transmission based on the modulation order, the code rate, and the spectral efficiency. 2. The method of claim 1, wherein the MCS table includes a plurality of entries corresponding to respective MCS indices, each of which has a modulation order of pi/2 binary phase-shift keying (BPSK) or quadrature phase-shift keying (QPSK). , one or more NTCRMs, with at least one entry each of 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. 3. The NTCRM of claim 2, wherein there are 64 entries in the MCS table. The method of claim 1, wherein the MCS table includes a plurality of entries corresponding to respective MCS indexes, and the entries of the MCS table are combined:
a substantially uniform grid of target signal-to-noise ratios (SNRs) corresponding to a target block error rate (BLER) of a corresponding MCS or a substantially uniform grid of spectral efficiencies of a corresponding MCS when used with a particular channel coding scheme;
A combination of code rate and modulation order for corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and
One or more NTCRM, providing the number of entries required to keep the bitwidth of the MCS field in the downlink control information below a predefined value. 5. The method of claim 4, wherein the entries in the MCS table measure the absolute decibel difference between the maximum or minimum SNR corresponding to the target BLER in the MCS table and the respective maximum or minimum SNR corresponding to the target BLER in the reference MCS table. One or more NTCRM, combined to further provide the maximum and minimum SNRs corresponding to the target BLER for MCSs such that a value is less than the uniform SNR grid step provided by the MCS table. 6. The NTCRM of claim 5, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 v16.4.0 for one or two MIMO layers. 4. The NTCRM of claim 3, wherein entries in the MCS table are combined to further provide a SNR grid step below a threshold. The method according to any one of claims 1 to 7, wherein the MCS table is:

One or more NTCRM, where I _MCS is the MCS index, Q _m is the modulation order, R is the code rate, and spectral efficiency (SE) per layer is the spectral efficiency per MIMO layer. 8. One or more NTCRM according to any one of claims 1 to 7, wherein the fixed number is 2. A device of user equipment (UE), said device
It is a memory that stores the modulation and coding scheme (MCS) table for two multiple input multiple output (MIMO) layers, and the MCS table is
a first set of entries with associated modulation orders and total spectral efficiencies equal to the corresponding entries of the reference MCS table with two MIMO layers; and
a memory comprising a second set of entries with associated modulation orders and total spectral efficiencies equal to corresponding entries in the reference MCS table with one MIMO layer; and
a processor circuit coupled to the memory, the processor circuit
receive an MCS index;
Based on the MCS index and the MCS table, determine a modulation order, code rate, and spectral efficiency for a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH);
and encode the PUSCH or decode the PDSCH for transmission based on the modulation order, the code rate, and the spectral efficiency. 11. The method of claim 10, wherein an entry in the reference MCS table with one MIMO layer is configured to: if the difference between the spectral efficiency of the entry and any entry from the first set of entries is less than a predetermined threshold, A device not included in the second set. 12. The device of claim 11, wherein the threshold value is an absolute value or a relative value. 11. The apparatus of claim 10, wherein the second set of entries have respective modulation orders and code rates to reproduce the corresponding spectral efficiency of the reference MCS table with one MIMO layer. 11. The device of claim 10, wherein the PDSCH or PUSCH is transmitted without MIMO layer adaptation. 15. The device according to any one of claims 10 to 14, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 v16.4.0. One or more non-transitory computer-readable media (NTCRM) storing instructions that, when executed, cause a Next-Generation Node B (gNB) to:
Determine an entry in a modulation and coding scheme (MCS) table for transmission with a fixed number of multiple input multiple output (MIMO) layers without MIMO layer adaptation, wherein the entry includes MCS index, modulation order, code rate, and spectral efficiency. Contains -;
transmit the MCS index to a user equipment (UE);
One or more NTCRMs to transmit or receive the transmission based on the modulation order, the code rate, and the spectral efficiency. 17. The method of claim 16, wherein the MCS table includes a plurality of entries corresponding to respective MCS indices, each modulation order being pi/2 binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK). , one or more NTCRMs, with at least one entry each of 16 Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM. 18. The NTCRM of claim 17, wherein there are 64 entries in the MCS table. The method of claim 16, wherein the MCS table includes a plurality of entries corresponding to respective MCS indexes, and the entries of the MCS table are combined:
a substantially uniform grid of target signal-to-noise ratios (SNRs) 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 code rate and modulation order for said corresponding spectral efficiency that minimizes BLER when used with a particular channel coding scheme; and
One or more NTCRM, providing the number of entries required to keep the bitwidth of the MCS field in downlink control information below a predefined value. 20. The method of claim 19, wherein the entries in the MCS table represent an absolute decibel difference between the maximum or minimum SNR corresponding to the target BLER in the MCS table and the respective maximum or minimum SNR corresponding to the target BLER in the reference MCS table. One or more NTCRM, combined to further provide the maximum and minimum SNRs corresponding to the target BLER for MCSs such that a value is less than the uniform SNR grid step provided by the MCS table. 21. The one or more NTCRM of claim 20, wherein the reference MCS table is MCS Table 1 or MCS Table 2 defined in 3GPP Technical Standard (TS) 38.214 v16.4.0 for one or two MIMO layers. 20. The NTCRM of claim 19, wherein entries in the MCS table are combined to further provide a SNR grid step below a threshold. 23. The method of any one of claims 16 to 22, wherein the MCS table is:

One or more NTCRM, where I _MCS is the MCS index, Q _m is the modulation order, R is the code rate, and spectral efficiency (SE) per layer is the spectral efficiency per MIMO layer. 23. One or more NTCRMs according to any one of claims 16 to 22, wherein the fixed number is 2.

Images