WO2021087986A1 - Modulation and coding scheme configuration method and apparatus - Google Patents

Abstract

Disclosed are an MCS configuration method and apparatus, wherein same can make it possible for a UE in a non-RRC connected state, when supporting qam64LowSE, to acquire a higher transmission reliability with a lower spectral efficiency and code rate. The method comprises: a terminal device receiving MCS configuration information, and determining, according to the MCS configuration information, an MCS configuration in an MCS table supported by the terminal device, wherein the MCS configuration information is used for indicating at least one of the following: an MSC configuration in a first MCS table and an MSC configuration in a second MCS table. In the present application, by means of defaulting or configuring or pre-defining the table used for MCS configuration information, a network device may not require any additional configuration indication information to indicate which MCS table is to be used, such that signaling overheads can be saved. Moreover, the network device can configure the MCS configuration in the MCS table corresponding to qam64LowSE without having knowledge of the capabilities of the terminal, such that the terminal device supporting qam64LowSE can acquire a higher transmission reliability with a lower spectral efficiency and code rate.

Description

Method and device for configuring modulation and coding scheme Technical field

This application relates to the field of communication technologies, and in particular to a modulation and coding scheme (modulation and coding scheme, MCS) configuration method and device.

Background technique

In the new radio (NR) system, there are two types of physical uplink shared channel (PUSCH) waveforms. Under each waveform, there are 3 MCS tables used to determine the MCS, namely: qam256 table, qam64LowSE table, qam64 table, among them, the modulation order supported by the qam256 table is up to 8, and the modulation order supported by the qam64 table and qam64LowSE table is up to 6, and the qam64LowSE table can support lower spectral efficiency and code rate.

Since the qam256 table and the qam64LowSE table are optional user equipment (UE) capabilities, not all UEs support the qam256 table and the qam64LowSE table. The base station can only acquire the capabilities of the UE in the radio resource control (Radio Resource Control, RRC) connected state. Therefore, for the UE in the RRC connected state, the base station can indicate the MCS table that can be used when the UE sends the PUSCH according to the capability of the UE. However, for a UE in a disconnected state, even if the UE supports the qam64LowSE table, the base station can only configure the UE to use the qam64 table to transmit PUSCH, and cannot use lower spectrum efficiency and code rate to obtain higher transmission reliability.

Summary of the invention

The present application provides an MCS configuration method and device, which can realize that a UE in a non-RRC connected state can use lower spectrum efficiency and code rate to obtain higher transmission reliability when supporting the qam64LowSE table.

In the first aspect, an MCS configuration method provided by an embodiment of the present application includes: a terminal device receives MCS configuration information, and determines the MCS configuration in an MCS table supported by the terminal device according to the MCS configuration information. Wherein, MCS configuration information is used to indicate at least one of the following: first MSC configuration, second MSC configuration, where the first MSC configuration is an MSC configuration in the first MCS table, and the second MSC configuration is in the second MCS table One MSC configuration. In the embodiment of this application, the table used by the MCS configuration information is defaulted or configured or pre-defined. Therefore, the network device may not need to configure the MCS table. The indication information is used to indicate which MCS table to use. The terminal device can be based on its own capabilities and MCS. The configuration information determines the MCS configuration, which can save signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, the first MCS table may be a qam64LowSE table, and the second MCS table may be a qam64 table.

In a possible design, the MCS configuration information is used to indicate the configuration of the first MSC. In the above design, the MCS configuration information is specified to use the qam64LowSE table by default or by agreement, and the network device may not need to additionally configure the MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the first MCS table and the first MSC configuration belongs to the second MCS table, the terminal device can The MCS index in the second MCS table is determined according to the MCS configuration information, and the MCS configuration indicated in the second MCS table by the MCS index is the same as the first MSC configuration. The terminal device determines the MCS configuration indicated by the MCS index in the second MCS table according to the MCS index. Through the above design, terminal devices that do not support the qam64LowSE table can use the MCS configuration of the qam64 table. In addition, the MCS configuration determined by the above design is the same as the MCS configuration indicated by the MCS configuration information, thereby avoiding the problem of PUSCH transmission failure caused by the difference of the MCS configuration of the network device and the terminal device.

In a possible design, when the MCS index configured by the first MSC in the first MCS table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to the second MCS table.

In a possible design, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the first MCS table and the first MSC configuration does not belong to the second MCS table, the terminal device The MCS configuration indicated by the MCS configuration information may not be used, or the terminal device may not use the PUSCH configuration corresponding to the MCS configuration information. Through the above design, when the qam64LowSE table is not supported, the terminal device abandons using the MCS configuration indicated by the MCS configuration information, which can avoid the problem of PUSCH transmission failure caused by the difference between the MCS configuration of the network device and the terminal device.

In a possible design, when the MCS index configured by the first MSC in the first MCS table belongs to the first index set, it means that the MCS configuration indicated by the MCS configuration information does not belong to the second MCS table.

In a possible design, the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table. In the above design, the manner in which the MCS configuration information indicates the subset of the MCS configuration can reduce the signaling overhead.

In a possible design, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device supports the first MCS table, the terminal device determines the first MSC in the first MCS table Configuration. Through the above design, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, when the terminal device selects the MCS configuration from the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the first MCS table, the terminal device does not use the first MSC configuration. Through the above design, when the qam64LowSE table is not supported, the terminal device abandons using the MCS configuration indicated by the MCS configuration information, which can avoid the problem of PUSCH transmission failure caused by the difference between the MCS configuration of the network device and the terminal device.

In a possible design, the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration. In the above design, the MCS configuration information is specified to use the qam64LowSE table and the qam64 table by default or by agreement, and the network device may not need to configure additional MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device supports the first MCS table, the terminal device determines the MCS configuration information in the first MCS table The first MCS configuration. In the above design, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the first MCS table, the terminal device uses the MCS configuration information in the second MCS table Determine the second MCS configuration. Through the above design, terminal devices that do not support the qam64LowSE table can use the MCS configuration of the qam64 table.

In one possible design, the first MCS configuration is the same as the second MCS configuration. Through the above design, the MCS configuration determined by the qam64LowSE table is the same regardless of whether the terminal device supports the qam64LowSE table, so that the MCS configuration of the network device and the terminal device are the same, which can avoid the problem of PUSCH transmission failure caused by the difference of the MCS configuration of the network device and the terminal device .

In a possible design, the MCS configuration information is also used to indicate the value of q in the MCS table, where q is the modulation order, and the value range is 0 or 1. Through the above design, the network equipment may not need to additionally configure the RRC parameter tp-pi2BPSK to determine the value of q, and the terminal equipment may determine the value of q according to the MCS configuration information, thereby saving signaling overhead.

In a second aspect, an MCS configuration method provided by an embodiment of the present application includes: a network device sends MCS configuration information. Wherein, MCS configuration information is used to indicate at least one of the following: first MSC configuration, second MSC configuration, where the first MSC configuration is an MSC configuration in the first MCS table, and the second MSC configuration is in the second MCS table One MSC configuration. In the embodiment of this application, the table used by the MCS configuration information is defaulted or configured or pre-defined. Therefore, the network device may not need to configure the MCS table. The indication information is used to indicate which MCS table to use. The terminal device can be based on its own capabilities and MCS. The configuration information determines the MCS configuration, which can save signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, the first MCS table may be a qam64LowSE table, and the second MCS table may be a qam64 table.

In a possible design, the MCS configuration information is used to indicate the configuration of the first MSC. In the above design, the MCS configuration information is specified to use the qam64LowSE table by default or by agreement, and the network device may not need to additionally configure the MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In a possible design, the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table. In the above design, the manner in which the MCS configuration information indicates the subset of the MCS configuration can reduce the signaling overhead.

In a possible design, the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration. In the above design, the MCS configuration information is specified to use the qam64LowSE table and the qam64 table by default or by agreement, and the network device may not need to configure additional MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

In one possible design, the first MCS configuration is the same as the second MCS configuration. Through the above design, the MCS configuration determined by the qam64LowSE table is the same regardless of whether the terminal device supports the qam64LowSE table, so that the MCS configuration of the network device and the terminal device are the same, which can avoid the problem of PUSCH transmission failure caused by the difference of the MCS configuration of the network device and the terminal device .

In a possible design, the MCS configuration information is also used to indicate the value of q in the MCS table, where q is the modulation order, and the value range is 0 or 1. Through the above design, the network equipment may not need to additionally configure the RRC parameter tp-pi2BPSK to determine the value of q, and the terminal equipment may determine the value of q according to the MCS configuration information, thereby saving signaling overhead.

In a third aspect, an MCS configuration method provided by an embodiment of the present application includes: a terminal device receives two PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, and the second PUSCH configuration corresponds to the second communication state, The two PUSCH configurations are used to configure the PUSCH resources in the two-step random access process; the terminal device uses the corresponding PUSCH configuration according to the communication state. In the embodiments of the present application, for different communication states, different service types and sizes can be used, and the same resource configuration parameters can use different value ranges and/or indicated content to more flexibly configure resources in different communication states.

In a possible design, the first communication state may be an RRC connected state. The second communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state.

In a possible design, the second communication state may be an RRC connected state. The first communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state.

In a possible design, the first communication state may be communication under a licensed spectrum, and the second communication state may be communication under an unlicensed spectrum.

In a possible design, the first communication state may be communication under an unlicensed spectrum, and the second communication state may be communication under a licensed spectrum.

In a possible design, the field length of the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may be different. In the above design, for different communication states, using different value ranges for the same resource configuration parameters can more flexibly configure resources in different communication states.

In a possible design, the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource may indicate different content. In the above design, for different communication states, the same resource configuration parameters can use different indication contents to more flexibly configure resources in different communication states.

In a possible design, when the terminal device uses the corresponding PUSCH configuration according to the communication state it is in, the terminal device may use the first PUSCH configuration when it is in the first communication state.

In a possible design, when the terminal device uses the corresponding PUSCH configuration according to the communication state it is in, the terminal device may use the second PUSCH configuration when it is in the second communication state.

In a fourth aspect, an MCS configuration method provided by an embodiment of the present application includes: a network device sends two PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, and the second PUSCH configuration corresponds to the second communication state. Two PUSCH configurations are used to configure PUSCH resources in a two-step random access process. In the embodiments of the present application, for different communication states, different service types and sizes can be used, and the same resource configuration parameters can use different value ranges and/or indicated content to more flexibly configure resources in different communication states.

In a possible design, the first communication state may be an RRC connected state. The second communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state.

In a possible design, the second communication state may be an RRC connected state. The first communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state.

In a possible design, the first communication state may be communication under a licensed spectrum, and the second communication state may be communication under an unlicensed spectrum.

In a possible design, the first communication state may be communication under an unlicensed spectrum, and the second communication state may be communication under a licensed spectrum.

In a possible design, the field length of the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may be different. In the above design, for different communication states, using different value ranges for the same resource configuration parameters can more flexibly configure resources in different communication states.

In a possible design, the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource may indicate different content. In the above design, for different communication states, the same resource configuration parameters can use different indication contents to more flexibly configure resources in different communication states.

In a fifth aspect, the present application provides an MCS configuration device, which may be a communication device, or a chip or chipset in the communication device, where the communication device may be a terminal device or a network device. The device may include a processing unit and a transceiving unit. When the device is a communication device, the processing unit may be a processor, and the transceiving unit may be a transceiver; the device may also include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit The instructions stored in the storage module are executed to enable the terminal device to perform the corresponding function in the first aspect or the third aspect, or to enable the network device to perform the corresponding function in the second aspect or the fourth aspect. When the device is a chip or chipset in a communication device, the processing unit can be a processor, and the transceiver unit can be an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage module to The terminal device is allowed to perform the corresponding function in the first aspect or the third aspect, or the network device is allowed to perform the corresponding function in the second aspect or the fourth aspect. The storage module can be a storage module (for example, register, cache, etc.) in the chip or chipset, or a storage module (for example, read-only memory, random memory, etc.) located outside the chip or chipset in the communication device. Fetch memory, etc.).

In a sixth aspect, an MCS configuration device is provided, which includes a processor, a communication interface, and a memory. The communication interface is used to transmit information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions. When the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes any design in the first aspect or the first aspect, or the third aspect. The MCS configuration method described in any one of the aspect or the third aspect is designed.

In a seventh aspect, an MCS configuration device is provided, which includes a processor, a communication interface, and a memory. The communication interface is used to transmit information, and/or messages, and/or data between the device and other devices. The memory is used to store computer-executable instructions. When the device is running, the processor executes the computer-executable instructions stored in the memory, so that the device executes any design in the second aspect or the second aspect, or the fourth aspect. The MCS configuration method described in any one of the aspect or the fourth aspect is designed.

In an eighth aspect, a computer storage medium provided by an embodiment of the present application. The computer storage medium stores program instructions. When the program instructions are run on a terminal device, the terminal device executes the first aspect of the embodiments of the present application and any of them. A possible design, or any design of the second aspect or the second aspect, or any design of the third aspect or the third aspect, or the method of any design of the fourth aspect or the fourth aspect.

In the ninth aspect, a computer program product provided by an embodiment of the present application, when the computer program product runs on a terminal device, makes the terminal device the first aspect of the embodiment of the present application and any possible design, or the second aspect or The method of any design in the second aspect, or any design in the third aspect or the third aspect, or any design in the fourth aspect or the fourth aspect.

The tenth aspect is a chip provided by an embodiment of the present application, which is coupled with a memory, and executes the first aspect and any possible design of the embodiment of the present application, or the third aspect or any one of the designs of the third aspect. method.

The eleventh aspect, a chip provided by an embodiment of the present application, the chip is coupled with a memory, and executes the second aspect and any possible design of the embodiment of the present application, or the third aspect or any design in the third aspect Methods.

In addition, the technical effects brought by the fifth aspect to the eleventh aspect can be referred to the description of the first aspect to the fourth aspect, and the details are not repeated here.

It should be noted that “coupled” in the embodiments of the present application means that two components are directly or indirectly combined with each other.

Description of the drawings

FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of this application;

FIG. 2 is a schematic flowchart of a four-step random access provided by an embodiment of this application;

FIG. 3 is a schematic flow chart of a two-step random access provided by an embodiment of this application;

4 is a schematic flowchart of an MCS configuration method provided by an embodiment of the application;

FIG. 5 is a schematic flowchart of another MCS configuration method provided by an embodiment of the application;

FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of this application;

FIG. 7 is a schematic structural diagram of another communication device provided by an embodiment of this application;

FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of this application;

FIG. 9 is a schematic structural diagram of a base station provided by an embodiment of the application.

Detailed ways

The MCS configuration method provided in this application can be applied to various communication systems, for example, the Internet of Things (IoT) system, the narrowband Internet of Things (NB-IoT) system, and the long-term evolution ( The long term evolution (LTE) system can also be a fifth-generation (5G) communication system, a hybrid architecture of LTE and 5G, a 5G NR system, and new communication systems that will appear in the development of future communications.

The terminal device involved in the embodiments of the present application is an entity on the user side for receiving or transmitting signals. The terminal device may be a device that provides voice and/or data connectivity to the user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. The terminal device can also be another processing device connected to the wireless modem. The terminal device can communicate with a radio access network (RAN). Terminal devices can also be called wireless terminals, subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, and access points , Remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment, UE), etc. The terminal equipment can be a mobile terminal, such as a mobile phone (or called a "cellular" phone) and a computer with a mobile terminal. For example, it can be a portable, pocket-sized, handheld, built-in computer or vehicle-mounted mobile device, which is connected with wireless The access network exchanges language and/or data. For example, the terminal device may also be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (personal digital assistant, PDA), and other equipment. Common terminal devices include, for example, mobile phones, tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, such as smart watches, smart bracelets, pedometers, etc., but this application is implemented Examples are not limited to this.

The network device involved in the embodiments of the present application is an entity on the network side for transmitting or receiving signals. The network equipment can also coordinate the attribute management of the air interface. For example, the network equipment can be an evolved Node B (eNB or e-NodeB) in LTE, a new radio controller (NR controller), or a gNode B (gNB) in a 5G system. ), it can be a centralized unit, it can be a new wireless base station, it can be a remote radio module, it can be a micro base station, it can be a relay, or it can be a distributed unit, It may be a reception point (transmission reception point, TRP) or transmission point (transmission point, TP) or any other wireless access device, but the embodiment of the present application is not limited thereto. Network equipment can cover one or more cells.

The method for determining random access resources provided by the embodiments of the present application can be applied to the communication system shown in FIG. 1, where the network equipment and UE1~UE3 form a single-cell communication system, and UE1~UE3 can send uplink data separately or at the same time To the network equipment, the network equipment can send downlink data to UE1 to UE3 separately or at the same time. It should be understood that FIG. 1 is only an exemplary illustration, and does not specifically limit the number of terminal devices, network devices, and the number of cells covered by the network devices included in the communication system.

The network architecture and business scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those of ordinary skill in the art will know that with the network With the evolution of the architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are equally applicable to similar technical problems.

In wireless communication systems such as LTE, 5G, and NR, the UE can enter the RRC connection state from the idle state or inactive state through random access, establish various bearers with network equipment, and obtain some necessary Resource and parameter configuration, and then communicate with network equipment.

At present, random access for UEs in wireless communication systems such as LTE and 5g NR usually requires four steps, as shown in Figure 2:

S201: The UE sends a random access preamble (random access preamble) to a network device, which may also be referred to as a first message (Msg1). The function of the random access preamble is to inform the network device that there is a random access request, and enable the network device to estimate the transmission delay between it and the UE, so that the network device can calibrate the uplink timing and pass the calibration information through the timing Inform the UE of the timing advance command.

S202: After detecting the random access preamble, the network device sends a random access response to the UE, which may also be referred to as a second message (Msg2). The random access response may include, but is not limited to, the sequence number of the random access preamble received in S201, timing advance instruction, uplink resource allocation information, and cell wireless network temporary identification.

S203. The UE receives a random access response. If the random access preamble indicated by the sequence number of the random access preamble in the random access response is the same as the random access preamble sent by the UE to the network device in S201, then The UE considers that the random access response is a random access response for the UE, that is, the UE has received the random access response of the UE. After receiving the random access response, the UE sends an uplink message on the uplink channel resources indicated by the random access response, for example, sending a PUSCH in Msg3, which is also called a third message (Msg3). Among them, Msg3 can carry a unique user ID.

S204: The network device receives the uplink message of the UE, and returns a conflict resolution message to the UE that has successfully accessed, which is also referred to as a fourth message (Msg4). The network device will carry the unique user identifier in Msg3 in the conflict resolution message to specify the UE that has successfully accessed, and other UEs that have not successfully accessed will re-initiate random access.

For the four-step random access process, when a UE in an idle state or an inactive state wants to perform uplink data transmission, it must first complete the aforementioned four information exchanges to enter the RRC connected state. For high-reliable and low-latency communications (URLLC) services, four information interactions will generate a high delay, which is not conducive to the low-latency requirements of URLLC. For large-scale machine type communications (mMTC) services, since most of the services are sporadic packets, the UE needs to perform a complete four-step random access every time and enter the RRC connection state to send data once, and then again Returning to the idle state or inactive state not only has a higher delay, but also has a serious signaling overhead.

In order to reduce the access delay and signaling overhead, a two-step random access process is currently proposed, as shown in Figure 3, in which the UE simultaneously sends a random access preamble to the network device in the first step. And data. In the second step, the network device sends a random access response to the UE. In the two-step random access process, on the one hand, the UE sends the random access preamble and data at the same time in the first step, which can greatly reduce the time delay of uplink data transmission. On the other hand, the network device does not need to send the scheduling information corresponding to Msg3 for the UE, so that the signaling overhead can be reduced. Generally, MsgA can be used to represent the first interactive message of two-step random access. MsgA is sent by the UE to the network device. The MsgA message includes the MsgA preamble part and the MsgA data part. The preamble is carried on the MsgA physical random access channel (physical random access channel). , PRACH) physical channel, and the data part is carried on the MsgA PUSCH physical channel for transmission. For ease of description, without affecting the context understanding, "preamble" is used below to refer to "MsgA preamble part", "data" refers to "MsgA data part", "PRACH" refers to "MsgA PRACH physical channel", " "PUSCH" refers to "MsgA PUSCH physical channel".

In the NR system, there are two types of PUSCH waveforms. When transform precoding (transform precoder) is activated, it is discrete fourier transform-spread OFDM (DFT-s-OFDM). ) Waveform, when transform precoding is not activated, it is a cyclic prefix orthogonal frequency division multiplexing (Cyclic Prefix, CP-OFDM) waveform. Under each waveform, there are 3 MCS tables used to determine MCS. The three MCS tables of CP-OFDM waveform are Table 5.1.3.1-1 (corresponding to qam64) and Table 5.1.3.1-2 in protocol TS38.214. (Corresponding to qam256), Table 5.1.3.1-3 (corresponding to qam64LowSE). The three MCS tables of the DFT-s-OFDM waveform are Table 6.1.4.1-1 (corresponding to qam64), Table 5.1.3.1-2 (corresponding to qam256), and Table 6.1.4.1-2 (corresponding to qam64) in the protocol TS38.214. Corresponds to qam64LowSE). Among them, qam256 supports a maximum modulation order of 8, qam64LowSE and qam64 supports a maximum modulation order of 6, and qam64LowSE can support lower spectral efficiency and bit rate. Exemplarily, the MCS table corresponding to qam64 when transform precoding is not activated may be as shown in Table 1. Among them, I _MCS is the MCS Index (MCS Index). Q _m is the modulation order (Modulation Order). R x[1024] is the target code rate.

Table 1

Exemplarily, when the transform precoding is not activated, the MCS table corresponding to qam64LowSE may be as shown in Table 2.

Table 2

Exemplarily, the MCS table corresponding to qam64 when transform precoding is activated may be as shown in Table 3.

table 3

Exemplarily, the MCS table corresponding to qam64LowSE when transform precoding is activated may be as shown in Table 4.

Table 4

When the terminal device is in the RRC connected state, the base station respectively instructs the PUSCH which MCS table to use to determine the MCS through the RRC parameters. For example, the base station can use the mcs-Table parameter to indicate which MCS table the PUSCH of the CP-OFDM waveform uses to determine the MCS configuration. For example, when the mcs-Table parameter is configured as "qam256", the PUSCH of the CP-OFDM waveform uses the MCS table corresponding to qam256 to determine the MCS configuration, and when the mcs-Table parameter is configured to "qam64LowSE", the PUSCH of the CP-OFDM waveform uses the MCS table corresponding to qam64LowSE (See Table 2) Determine the MCS configuration. For another example, the base station can use the mcs-TableTransformPrecoder parameter to indicate which MCS table the PUSCH of the DFT-s-OFDM waveform uses to determine the MCS. For example, when the mcs-TableTransformPrecoder parameter is configured as "qam256", the PUSCH of the DFT-s-OFDM waveform uses qam256. The MCS table determines the MCS configuration. When the mcs-TableTransformPrecoder parameter is configured as "qam64LowSE", the PUSCH of the DFT-s-OFDM waveform uses the MCS table corresponding to qam64LowSE (see Table 4) to determine the MCS configuration.

The base station can also use the MCS-cell-radio network tempory identity (MCS-C-RNTI) to indicate the use of the qam64LowSE table. For example, when the base station configures the UE with MCS-C-RNTI and instructs the UE to use If the MCS-C-RNTI schedules PUSCH, the UE uses the MCS table corresponding to qam64LowSE to determine the MCS configuration. If the base station is not configured with mcs-Table and mcs-TableTransformPrecoder, and MCS-C-RNTI is not used to schedule PUSCH, the UE can use qam64 by default Corresponding MCS table.

Since qam256 and qam64LowSE are optional user equipment (UE) capabilities, not all UEs support qam256 and qam64LowSE. The base station can only acquire the capabilities of the UE in the radio resource control (Radio Resource Control, RRC) connected state. Therefore, for the UE in the RRC connected state, the base station can indicate the MCS table that can be used when the UE sends the PUSCH according to the capability of the UE. But for a non-connected UE, even if the UE supports qam64LowSE, the base station can only configure the UE to use the MCS in the MCS table corresponding to qam64 to send PUSCH, and cannot use lower spectrum efficiency and code rate to obtain higher transmission reliability. .

Based on this, the embodiments of the present application provide an MCS configuration method and device, which can configure the qam64LowSE table for terminal devices in a non-RRC connected state, so that when a non-RRC connected terminal device supports the qam64LowSE table, it can be based on the qam64LowSE table. The table determines the MCS configuration, and then lower spectrum efficiency and code rate can be used to obtain higher transmission reliability. Among them, the method and the device are based on the same inventive concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.

It should be understood that in the embodiments of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And/or" describes the association relationship of the associated object, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the associated objects before and after are in an "or" relationship. "The following at least one (item)" or similar expressions refers to any combination of these items, including any combination of single item (item) or plural items (item). For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c It can be single or multiple. In addition, it should be understood that in the description of this application, words such as "first", "second", and "third" are only used for the purpose of distinguishing description, and cannot be understood as indicating or implying relative importance. Nor can it be understood as indicating or implying order.

The embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

Example one:

As shown in FIG. 4, an MCS configuration method provided by this embodiment of the present application may be applied to the communication system shown in FIG. 1. Specifically, the method may be applied to a terminal device. The MCS configuration method may specifically include:

S401: The network device sends MCS configuration information to the terminal device. Correspondingly, the terminal device receives the MCS configuration information. MCS configuration information is used to indicate at least one of the following: first MSC configuration, second MSC configuration, where the first MSC configuration is one MSC configuration in the first MCS table, and the second MSC configuration is one in the second MCS table MSC configuration.

In an exemplary description, the first MCS table may be the MCS table of qam64LowSE, or may also be referred to as the MCS table corresponding to qam64LowSE, or may also be referred to as the qam64LowSE table, or, the first MCS table may refer to the protocol TS38. Table 5.1.3.1-3 in 214 or Table 6.1.4.1-2 in protocol TS38.214. The second MCS table may be the MCS table of qam64, or may also be called the MCS table corresponding to qam64, or may also be called the qam64 table, or the first MCS table may refer to Table 5.1.3.1 in the protocol TS38.214 -1 or Table 6.1.4.1-1 in TS38.214. For the convenience of description, the first MCS table is collectively referred to as the "qam64LowSE table", and the second MCS table is collectively referred to as the "qam64 table".

It should be understood that the qam64LowSE table and the qam64 table are only exemplary naming, and they can be named other in specific implementation or future communication development. For example, the qam64LowSE table can also be named A, and the qam64 table can also be named B, as long as A Is the MCS table related to qam64LowSE, and B is the MCS table related to qam64, then A can be understood as the qam64LowSE table in the embodiment of the application, and B is understood as the qam64 table in the embodiment of the application.

S402: The terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, and the MCS table is a qam64LowSE table or a qam64 table.

Further, the terminal device may also determine the PUSCH resource configuration corresponding to the MCS configuration.

Three exemplary descriptions of MCS configuration information are introduced below.

In the first exemplary description, for each PUSCH waveform, one MCS table can be used by default or protocol predefined. For example, the default or protocol pre-defined use of the qam64LowSE table can be understood as the default or protocol pre-defined MCS configuration information indicating an MCS configuration in the qam64LowSE table. For another example, the default or protocol pre-defined use of the qam64 table can be understood as the default or protocol pre-defined MCS configuration information indicating an MCS configuration in the qam64 table.

The MCS configuration information may be the MCS index, that is, I _MCS . For example, the qam64LowSE table is used by default or predefined by the protocol, and the MCS configuration information may be the MCS index in the qam64LowSE table. For example, the qam64 table is used by default or predefined by the protocol, and the MCS configuration information may be the MCS index in the qam64 table.

Taking the default or protocol predefined MCS configuration information indicating an MCS configuration in the qam64LowSE table as an example, step S402 will be described with reference to the first exemplary description.

In a possible implementation manner, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the qam64LowSE table, then in the case that the first MSC configuration belongs to the qam64 table, the terminal device The MCS index in the qam64 table can be determined according to the MCS configuration information. The MCS configuration indicated by the MCS index in the qam64 table is the same as the first MSC configuration, and then the MCS configuration indicated by the MCS index is determined in the qam64 table according to the MCS index.

In some embodiments, when the terminal device determines the MCS index in the qam64 table according to the MCS configuration information, it can determine the MCS in the qam64 table according to the correspondence between the MCS index in the qam64LowSE table and the MCS index in the qam64 table, and the MCS configuration information. index. Taking the above Table 1 and Table 2 as examples, the MCS configuration with index 0 in Table 1 is the same as the MCS configuration with index 6 in Table 2, and the MCS configuration with index 1 in Table 1 is the same as the MCS configuration with index 7 in Table 2. The same, the MCS configuration with index 2 in Table 1 is the same as the MCS configuration with index 8 in Table 2, and the MCS configuration with index 3 in Table 1 is the same as the MCS configuration with index 9 in Table 2, ..., in Table 1 The MCS configuration with index 8 is the same as the MCS configuration with index 14 in Table 2. Therefore, if the MCS configuration information is the MCS index 6 in the qam64LowSE table, it can be determined that the MCS index corresponding to the qam64 table is 0. If the MCS configuration information is the MCS index 7 in the qam64LowSE table, it can be determined that the MCS index corresponding to the qam64 table is 1. If the MCS configuration information is the MCS index 8 in the qam64LowSE table, it can be determined that the MCS index corresponding to the qam64 table is 2. ……. If the MCS configuration information is the MCS index 14 in the qam64LowSE table, it can be determined that the MCS index corresponding to the qam64 table is 8.

Exemplarily, the correspondence between the MCS index in the qam64LowSE table and the MCS index in the qam64 table may be that the MCS index i in the qam64LowSE table corresponds to the MCS index i-6 in the qam64 table.

In another possible implementation manner, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the qam64LowSE table but the terminal device saves the qam64LowSE table, the terminal device can determine it according to the qam64LowSE table Whether the MCS configuration indicated by the MCS configuration information belongs to the qam64 table, or the terminal device can determine whether it supports the MCS configuration indicated by the MCS configuration information according to the qam64LowSE table. In the case that the first MSC configuration belongs to the qam64 table, the terminal device can according to the saved qam64LowSE The table determines the MCS configuration information indicated by the MCS configuration information.

In another possible implementation manner, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the qam64LowSE table, if the first MSC configuration does not belong to the qam64 table, the terminal The device may not use the MCS configuration indicated by the MCS configuration information, or the terminal device may not use the PUSCH configuration associated with the MCS configuration information.

In another possible implementation manner, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device supports the qam64LowSE table, the terminal device can determine the MCS configuration according to the MCS configuration information in the qam64LowSE table .

In another possible implementation manner, when the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device does not support the qam64LowSE table, the terminal device can determine the MCS in the qam64 table according to the MCS configuration information Configuration. If the terminal device supports the qam64LowSE table, the terminal device can determine the MCS configuration in the qam64LowSE table according to the MCS configuration information.

Exemplarily, a method for judging whether the first MSC configuration belongs to the qam64 table may be: when the MCS index configured by the first MSC in the qam64LowSE table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to qam64 table. Otherwise, the MCS configuration indicated by the MCS configuration information does not belong to the qam64 table.

Exemplarily, the first index set may be {6, 7, 8, 9, 10, 11, 12, 13, 14}. If the MCS configuration information is the MCS index in the qam64LowSE table, it may be the case that the MCS configuration information belongs to the first index set, and the MCS configuration indicated by the MCS configuration information belongs to the qam64 table. For example, when the MCS configuration information is equal to 8, the qam64LowSE table The MCS configuration with an internal index of 8 belongs to the qam64 table, and it can also be understood that the MCS configuration with an index of 8 in the qam64LowSE table also exists in the qam64 table.

Or, another method for judging whether the first MSC configuration belongs to the qam64 table may be: when the MCS index configured by the first MSC in the qam64LowSE table belongs to the second index set, the MCS configuration indicated by the MCS configuration information does not belong to qam64 table. Otherwise, the MCS configuration indicated by the MCS configuration information belongs to the qam64 table. Exemplarily, the second index set may be {1,2,3,4,5,15}. If the MCS configuration information is the MCS index in the qam64LowSE table, it may be that when the MCS configuration information belongs to the second index set, the MCS configuration indicated by the MCS configuration information does not belong to the qam64 table. For example, when the MCS configuration information is equal to 4, qam64LowSE The MCS configuration with the index 4 in the table does not belong to the qam64 table, and it can also be understood that the qam64 table does not include the MCS configuration with the index 4 in the qam64LowSE table.

Or, another method for judging whether the first MSC configuration belongs to the qam64 table may be: in the case that the MCS index configured by the first MSC in the qam64LowSE table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to qam64 table. In the case that the MCS index configured by the first MSC in the qam64LowSE table belongs to the second index set, the MCS configuration indicated by the MCS configuration information does not belong to the qam64 table.

In an implementation manner, the range indicated by the MCS configuration information may be the full set of MCS configurations in the qam64LowSE table, or may be a subset of the MCS configurations in the qam64LowSE table. For example, each MCS table has 32 MCSs, and the MCS configuration information can be 5 bits, which can indicate any one of the 32 MCS configurations. Alternatively, the MCS configuration information may also be less than 5 bits, and then one MCS configuration may be indicated from a subset of 32 MCS configurations, and the subset may be predefined or configured by a network device. For example, the MCS configuration information may be 4 bits, the MCS subset is 16 MCS configurations in the MCS table, and the 16 MCS configurations may be the first 16 items, or the last 16 items, or the predefined 16 items in the MCS table. By means of the MCS configuration information indicating the subset of the MCS configuration, the signaling overhead can be reduced.

For example, taking the PUSCH transform precoding not activated, that is, the CP-OFDM waveform as an example, the MCS configuration information may be 4 bits, which may indicate one of the first 16 MCS configurations in the qam64LowSE table.

In the second exemplary description, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may be predefined.

For example, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may include MCS configurations belonging to the qam64LowSE table but not belonging to the qam64 table, that is, the MCS configuration information only indicates the first MCS configuration.

Alternatively, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may also include an MCS configuration belonging to the qam64LowSE table and an MCS configuration belonging to the qam64 table, that is, the MCS configuration information indicates the first MCS configuration and the second MCS configuration. Two MCS configuration. Wherein, the first MCS configuration and the second MCS configuration may be the same or different, and there is no specific limitation here. Wherein, when the first MCS configuration is the same as the second MCS configuration, it can be understood that the correspondence between the MCS configuration information and at least one MCS configuration in the at least one MCS table may also include the MCS configuration belonging to both the qam64LowSE table and the qam64 table.

Alternatively, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may also include the MCS configuration belonging to the qam64 table but not the qam64LowSE table, that is, the MCS configuration information only indicates the second MCS configuration.

Exemplarily, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may be as shown in Table 5.

table 5

The correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may include the MCS configuration belonging to the qam64LowSE table but not the qam64 table, that is, when the MCS configuration information only indicates the first MCS configuration, for example, the MCS configuration in Table 5 Information 0, MCS configuration information 1, MCS configuration information 2. The terminal device determines the MCS configuration method in the MCS table supported by the terminal device according to the MCS configuration information. For details, please refer to the relevant description in the first exemplary description above. Repeat it again.

The correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may also include an MCS configuration belonging to the qam64LowSE table and an MCS configuration belonging to the qam64 table, that is, the MCS configuration information indicates the first MCS configuration and the second MCS configuration. During configuration, for example, MCS configuration information 3, MCS configuration information 4, MCS configuration information 5, MCS configuration information 6, MCS configuration information 7 in Table 5. When the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, if the terminal device supports the qam64LowSE table, the terminal device can determine the first MCS configuration according to the MCS configuration in the qam64LowSE table. If the terminal device does not support the qam64LowSE table, the terminal device can determine the second MCS configuration according to the MCS configuration in the qam64 table.

For example, assuming that the MCS configuration information is MCS configuration information 4 in Table 5 above, if the terminal device supports the qam64LowSE table, the terminal device can use the MCS configuration with the MCS index of 8 in the qam64LowSE table. If the terminal device does not support the qam64LowSE table, the terminal device can use the MCS configuration with the MCS index of 2 in the qam64 table.

The correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may also include the MCS configuration belonging to the qam64 table but not the qam64LowSE table, that is, when the MCS configuration information only indicates the second MCS configuration, for example, the MCS in Table 5 Configuration information 8, MCS configuration information 9. When the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, the terminal device can determine the second MCS configuration according to the MCS configuration in the qam64 table.

In the third exemplary description, the MCS configuration information and the MCS index of at least one MCS configuration in the at least one MCS table satisfy a preset correspondence relationship. For example, the MCS configuration information i can correspond to the MCS configuration in the qam64LowSE table or the MCS index in the qam64 table with a*(ib)+c, a, b, and c are natural numbers, and the values of a, b, and c are predefined, or , It can also be configured by network equipment. Among them, for the qam64LowSE table and the qam64 table, the value of a may be the same or different. For example, for the qam64LowSE table and the qam64 table, the value of a is both 2. Or, for the qam64LowSE table, the value of a can be 1, and for the qam64 table, the value of a can be 2. For the qam64LowSE table and the qam64 table, the value of b can be the same or different. For example, for the qam64LowSE table and the qam64 table, the value of b is both 1. Or, for the qam64LowSE table, the value of b can be 1, and for the qam64 table, the value of b can also be 3.

For the qam64LowSE table and the qam64 table, the value of c can be the same or different. For example, for the qam64LowSE table and the qam64 table, the value of c is both 0. Or, for the qam64LowSE table, the value of c can be 1, and for the qam64 table, the value of c can be 2.

Exemplarily, when the terminal device supports the qam64LowSE table, the MCS configuration information i can correspond to the MCS configuration in the qam64LowSE table whose MCS index is 2*i. When the terminal device does not support the qam64LowSE table, the MCS configuration information i can correspond to the MCS in the qam64 table MCS configuration with index 2*(i-3).

In the embodiment of this application, the table used by the MCS configuration information is defaulted or configured or pre-defined. Therefore, the network device may not need to configure the MCS table. The indication information is used to indicate which MCS table to use. The terminal device can be based on its own capabilities and MCS. The configuration information determines the MCS configuration, which can save signaling overhead. In addition, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, so that the terminal device supporting the qam64LowSE table can use lower spectrum efficiency and bit rate to obtain higher transmission reliability.

When PUSCH transform precoding is activated, that is, when DFT-s-OFDM waveform PUSCH, the modulation order of some MCS configurations in the MCS table is parameter q, as in Table 3, the modulation order of MCS configuration with _{I MCS of 0, I MCS} The modulation order of the MCS configuration with 1, the modulation order of the MCS configuration with I _MCS of 0 in Table 4, the modulation order of the MCS configuration with I _MCS of 1, and the modulation order of the MCS configuration with I _MCS of 2, etc. Among them, q=1, representing pi/2 binary phase shift keying (BPSK), and q=2, representing quadrature phase shift keying (QPSK).

If the MCS configuration information indicates the MCS configuration in the MCS table corresponding to the PUSCH of the DFT-s-OFDM waveform, and there is a parameter q for the modulation order in the MCS configuration. Regarding the value of the parameter q, one possible implementation is that the value of q can be defaulted. For example, the default value of q can be 1, which means pi/2BPSK, or the default value of q is 2, which means QPSK.

Another possible implementation is that the value of q can be determined according to the RRC parameter tp-pi2BPSK sent by the network device. When tp-pi2BPSK is activated, q=1, which means pi/2BPSK. When tp-pi2BPSK is not activated, q=2, which means QPSK.

Another possible implementation manner is that the value of q can be indicated through MCS configuration information. For example, the MCS configuration with the parameter q of the modulation order is indicated by two MCS configuration information respectively, that is, one MCS configuration information indicates the MCS configuration and the value of q is 1, and the other MCS configuration information indicates the MCS configuration and q The value is 2.

As an example, take the qam64 table of the DFT-s-OFDM waveform, as shown in Table 3, as an example, there is a parameter q in the first two MCS configurations, and the MCS configuration information can be 4 bits, then the MCS configuration information is i (0≤i ≤1) indicates that the MCS index in the qam64 table is the MCS configuration of i and q=2. When the MCS configuration information is i (2≤i≤9), it indicates the MCS configuration whose MCS index in the qam64 table is i. When the MCS configuration information is i (10≤i≤11), it indicates that the MCS index in the qam64 table is the MCS of i-10 and q=1. MCS configuration information i (12≤i≤15) may be a reserved item.

In another example, the value of the parameter q may be included in the corresponding relationship between the MCS configuration information and the at least one MCS configuration in the at least one MCS table in the second exemplary description. For example, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may include the MCS configuration belonging to the qam64LowSE table but not the qam64 table and the value of q is 1, or it may also include the MCS configuration belonging to the qam64LowSE table but not belonging to the qam64LowSE table. The MCS configuration of the qam64 table and the value of q is 2.

Alternatively, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may further include an MCS configuration belonging to the qam64LowSE table, an MCS configuration belonging to the qam64 table, and the value of q of each MCS configuration.

Alternatively, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may also include the MCS configuration belonging to the qam64 table but not the qam64LowSE table and the value of q is 1, or it may also include the MCS configuration belonging to the qam64 table but not It belongs to the MCS configuration of the qam64LowSE table and the value of q is 2.

Exemplarily, the correspondence between the MCS configuration information and the at least one MCS configuration in the at least one MCS table may be as shown in Table 6.

Table 6

In the above manner, the network device may not need to configure the additional RRC parameter tp-pi2BPSK to determine the value of q, and the terminal device may determine the value of q according to the MCS configuration information, thereby saving signaling overhead.

Optionally, the network device may send multiple MCS configuration information to the terminal device.

In an implementation manner, the terminal device may sequentially determine the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information. For example, the network device may send three MCS configuration information to the terminal device, and the terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the first MCS configuration information. If the MCS configuration is determined based on the first MCS configuration information, the MCS configuration can be used. If it is determined not to use the MCS configuration information indicated by the first MCS configuration information, the MCS configuration can be determined in the MCS table supported by the terminal device according to the second MCS configuration information. If the MCS configuration is determined based on the second MCS configuration information, the MCS configuration can be used. If it is determined not to use the MCS configuration information indicated by the second MCS configuration information, the MCS configuration can be determined in the MCS table supported by the terminal device according to the third MCS configuration information.

In another implementation manner, the terminal device can respectively determine the MCS configuration in the MCS table supported by the terminal device according to multiple MCS configuration information, so that the terminal device can select an MCS configuration from the determined MCS configuration according to actual needs, or the terminal The device may also randomly select an MCS configuration from the determined MCS configurations, or the terminal device may also select an MCS configuration from the determined MCS configurations under preset rules. Exemplarily, the preset rule may be to select one MCS configuration according to the sequence of receiving time of the MCS configuration information. Or, the preset rule is to select according to the spectrum efficiency of the MCS configuration information. Or, the preset rule is to select according to the code rate of the MCS configuration information. Or, the preset rule is to select according to the spectral efficiency and code rate of the MCS configuration information, and so on.

For example, the network device may send 5 MCS configuration information to the terminal device, and the terminal device determines 3 MCS configurations in the MCS table supported by the terminal device according to the 5 MCS configuration information. The terminal device can select one MCS configuration among the three MCS configurations.

The above-mentioned embodiments can be used in the RRC connected state, and can also be used in the RRC idle state and the RRC inactive state. The MCS configuration modes of the RRC connected state and the non-RRC connected state (RRC idle state and RRC inactive state) can be the same or different. For example, in the non-RRC connected state, the MCS configuration method in the above embodiment is used. In the RRC connected state, the base station configures the MCS table indication information to indicate which MCS table to use, and configures the MCS configuration information to indicate an MCS in the MCS table. , Configure tp-pi2BPSK to indicate the value of parameter q. In the RRC connected state, the network equipment can schedule UEs with the same UE capability in the same BWP. For example, the network device may only schedule the UEs supporting qam64LowSE in the first BWP, and in the first BWP, the network device may use MCS table indication information to indicate which MCS table to use. For another example, the network device may only schedule UEs supporting pi/2BPSK in the first BWP, and in the first BWP, the network device may use tp-pi2BPSK to indicate the value of the parameter q. For another example, the MCS table of qam64 or qam64LowSE is used by default in the non-RRC connection state, and the MCS configuration mode in the above embodiment is used in the RRC connection state.

Embodiment two:

As shown in Fig. 5, another MCS configuration method provided by this embodiment of the application can be applied to the communication system shown in Fig. 1. Specifically, the method can be applied to a terminal device. The MCS configuration method may specifically include:

S501: The terminal device receives two PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, the second PUSCH configuration corresponds to the second communication state, and the two PUSCH configurations are used to configure PUSCH resources in the two-step random access process.

Exemplarily, the first communication state may be an RRC connected state, and the second communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state. Alternatively, the second communication state may be an RRC connected state, and the first communication state may be a non-RRC connected state, such as an RRC idle state or an RRC inactive state. In the following, the first communication state is the RRC connected state and the second communication state is the non-RRC connected state as an example for description.

Among them, the first PUSCH configuration and the second PUSCH configuration have the same type of parameter, and the field length of the parameter in the first PUSCH configuration and the field length in the second PUSCH resource may be different. The content indicated by the parameter in the first PUSCH configuration and the content indicated in the second PUSCH resource may also be different.

For example, the value ranges of the MCS configuration information in the first PUSCH configuration and the second PUSCH configuration may be the same or different. For example, the MCS configuration information in the first PUSCH configuration is 5 bits, and the value range is 0 to 31, and the MCS configuration information in the second PUSCH configuration is 4 bits, and the value range is 0 to 15.

The content indicated by the MCS configuration information in the first PUSCH configuration and the second PUSCH configuration may be the same or different, and it may also be understood that the interpretation of the MCS configuration information may be the same or different for the first PUSCH configuration and the second PUSCH configuration. For example, the MCS configuration information i in the first PUSCH configuration may indicate the MCS whose MCS index is i in the MCS table, and the MCS configuration information i in the second PUSCH configuration may indicate the MCS whose MCS index is 2*i in the MCS table.

It can be understood that the value range and/or the indicated content of the other configuration information in the first PUSCH configuration and the second PUSCH configuration may also be different.

For example, the time domain resource configuration information of msgA PUSCH in the second PUSCH configuration may be 4 bits, with a value range of 0-15, indicating one item in a predefined or time domain resource configuration table (list) configured by the base station, Each item in the time domain resource configuration table (list) indicates at least one of the following information: start symbol, length, PUSCH mapping type, time interval between PRACH and PUSCH, and msgA PUSCH time domain resources in the first PUSCH configuration The configuration information can be 7 bits, with a value range of 0 to 127, indicating the value of the starting symbol and length after joint coding. The msgA PUSCH time domain resource configuration information in the first PUSCH configuration can also include PUSCH mapping type configuration information and PRACH Time interval configuration information with PUSCH.

For another example, the frequency domain resource size of msgA PUSCH in the second PUSCH configuration can be 2 bits, and the value range is {1,2,3,6}RB, and the time domain resource configuration information of msgA PUSCH in the first PUSCH configuration can also be It is 2 bits and the value range is {2,4,6,12}RB, or the time domain resource configuration information of msgA PUSCH in the first PUSCH configuration can be 4 bits, and the value range is {1,2,3,4 ,5,6,8,9,10}RB.

For another example, in the second PUSCH configuration, the subcarrier interval of the preamble of the two-step random access and the target received power of the preamble do not need to be configured, and the corresponding parameters of the four-step random access are used. In the first PUSCH configuration, four-step random access resources may not be configured on some BWPs. If two-step random access resources are configured on these BWPs, the subcarrier interval of the preamble and the target received power of the preamble need to be configured independently.

For another example, the first PUSCH configuration information includes Phase Tracking Reference Signals (PTRS) configuration information, and the second PUSCH configuration information does not include PTRS configuration information. Or, the first PUSCH configuration information does not include PTRS configuration information, and the second PUSCH configuration information includes PTRS configuration information. Or both the first PUSCH configuration information and the second PUSCH configuration information include PTRS configuration information. Or neither the first PUSCH configuration information nor the second PUSCH configuration information includes the PTRS configuration information. The PTRS configuration information may include, but is not limited to, the following information: frequency domain density configuration information, time domain density configuration information, PTRS port configuration information, resource unit offset configuration information, PTRS power configuration information, and sample density configuration information.

In addition, in the unlicensed frequency band and the licensed frequency band, the value range and/or interpretation of the resource configuration parameters of the two-step random access may also be different.

For example, in the licensed frequency band, the guard interval of msgA PUSCH can be 1 bit, and the value range is 0 to 1 OFDM symbol, or 2 bits, and the value range is 0 to 3 OFDM symbols. In the unlicensed frequency band, the guard interval of msgA PUSCH can be 2 bits, the value range is {0,2,4,6}OFDM symbols.

S502: The terminal device uses a corresponding PUSCH configuration according to the communication state it is in.

In specific implementation, the terminal device may use the first PUSCH configuration when it is in the RRC connected state. The terminal device can use the second PUSCH configuration when in the RRC idle state or the RRC inactive state.

In the embodiment of this application, in the RRC connected state and the non-RRC connected state, due to the different service types and service sizes, the same resource configuration parameters use different value ranges and/or indicated content to allow more flexible configuration of the RRC connected state and Non-RRC connected resources.

It should be noted that the above two embodiments can be implemented as an independent solution respectively, or can be combined as a single solution, and this application does not make specific limitations.

In the above-mentioned embodiments provided by the present application, the methods provided by the embodiments of the present application are respectively introduced from the perspective of network equipment, terminal equipment, and interaction between the network equipment and the terminal equipment. In order to realize the functions in the methods provided in the above embodiments of the present application, the network equipment and the terminal equipment may include hardware structures and/or software modules, which are implemented in the form of hardware structures, software modules, or hardware structures plus software modules. . Whether a certain function of the above-mentioned functions is executed by a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraint conditions of the technical solution.

As shown in FIG. 6, based on the same technical concept, an embodiment of the present application also provides an MCS configuration device 600. The device 600 may be a terminal device or a network device, or a device in a terminal device or a network device (for example, A chip or a chip system or a chip set or a part of a chip used to perform related method functions), or a device that can be used with terminal equipment or network equipment. In one design, the device 600 may include modules that perform one-to-one correspondence of the methods/operations/steps/actions performed by the terminal equipment or network equipment in the foregoing method embodiments. The modules may be hardware circuits, software, or It is realized by hardware circuit combined with software. In one design, the device may include a processing module 601 and a communication module 602.

In an implementation manner, the MCS configuration device may be specifically used to implement the method executed by the terminal device in the embodiment of FIG. 4. The communication module 602 is configured to receive MCS configuration information, where the MCS configuration information is used to indicate at least one of the following: a first MSC configuration, a second MSC configuration, and the first MSC configuration is in the first MCS table The second MSC configuration is an MSC configuration in the second MCS table. The processing module 601 is configured to determine an MCS configuration in a supported MCS table according to the MCS configuration information received by the communication module 602, where the MCS table is the first MCS table or the second MCS table.

In an exemplary description, the MCS configuration information is used to indicate the configuration of the first MSC. The processing module 601 is specifically configured to: if the first MCS table is not supported and the first MSC configuration belongs to the second MCS table, determine the MCS index in the second MCS table according to the MCS configuration information, and the MCS index is indicated in the second MCS table The MCS configuration is the same as the first MSC configuration; the MCS configuration indicated by the MCS index is determined in the second MCS table according to the MCS index.

Exemplarily, when the MCS index configured by the first MSC in the first MCS table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to the second MCS table.

In another exemplary description, the MCS configuration information is used to indicate the first MSC configuration; the processing module 601 is specifically used to: if the first MCS table is not supported and the first MSC configuration does not belong to the second MCS table, the MCS configuration is not used The MCS configuration indicated by the message.

Exemplarily, when the MCS index configured by the first MSC in the first MCS table belongs to the first index set, it means that the MCS configuration indicated by the MCS configuration information does not belong to the second MCS table.

Optionally, the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table.

In another exemplary description, the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration. The processing module 601 is specifically configured to: if the first MCS table is supported, determine the first MCS configuration according to the MCS configuration information in the first MCS table; or, if the first MCS table is not supported, then according to the second MCS table The MCS configuration information determines the second MCS configuration.

Wherein, the first MCS configuration and the second MCS configuration may be the same.

Exemplarily, the MCS configuration information may also be used to indicate the value of q in the MCS table, where q is the modulation order, and the value range is 0 or 1.

In another implementation manner, the MCS configuration apparatus may be specifically used to implement the method executed by the network device in the embodiment of FIG. 4. Wherein, the communication module 602 is configured to send MCS configuration information, where the MCS configuration information is used to indicate at least one of the following: a first MSC configuration, a second MSC configuration, wherein the first MSC configuration is in the first MCS table The second MSC configuration is an MSC configuration in the second MCS table.

In an exemplary description, the MCS configuration information is used to indicate the configuration of the first MSC.

Optionally, the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table.

In another exemplary description, the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration.

Wherein, the first MCS configuration and the second MCS configuration may be the same.

Exemplarily, the MCS configuration information may also be used to indicate the value of q in the MCS table, where q is the modulation order, and the value range is 0 or 1.

In another implementation manner, the MCS configuration apparatus may be specifically used to implement the method executed by the terminal device in the embodiment of FIG. 5. Among them, the communication module 602 is used to receive two PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, the second PUSCH configuration corresponds to the second communication state, and the two PUSCH configurations are used to configure the two-step random access process The processing module 601 is used to use the corresponding PUSCH configuration according to the communication state.

Exemplarily, the field length of the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may be different.

The content indicated by the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may also be different.

The processing module 601 may be specifically configured to: use the first PUSCH configuration when in the first communication state; or, use the second PUSCH configuration when in the second communication state.

In another implementation manner, the MCS configuration apparatus may be specifically used to implement the method executed by the network device in the embodiment of FIG. 5. The communication module 602 is used to send two PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, the second PUSCH configuration corresponds to the second communication state, and the two PUSCH configurations are used to configure the two-step random access process PUSCH resources.

Exemplarily, the field length of the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may be different.

The content indicated by the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource may also be different.

The processing module 601 and the communication module 602 may also be used to execute other corresponding steps or operations performed by the terminal device or the terminal device in the foregoing method embodiment, which will not be repeated here.

The division of modules in the embodiments of this application is illustrative, and it is only a logical function division. In actual implementation, there may be other division methods. In addition, the functional modules in the various embodiments of this application can be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.

As shown in FIG. 7, an apparatus 700 provided in an embodiment of the application is used to implement the function of the MCS configuration apparatus 600 in the foregoing method. The device can be a communication device, or a device in a communication device (for example, a chip or a chip system or a chip set or a part of a chip used to perform related method functions), or a device that can be used in conjunction with a communication device. The device can be a terminal device or a network device. Among them, the device may be a chip system. In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices. The apparatus 700 includes at least one processor 720, configured to implement the functions of the terminal device or the network device in the method provided in the embodiment of the present application. The device 700 may also include a communication interface 710. In the embodiment of the present application, the communication interface 710 may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces for communicating with other devices through a transmission medium. For example, when the function of the terminal device is implemented, the communication interface 710 is used by the device in the device 700 to communicate with other devices. Illustratively, the other device may be a network device. The processor 720 uses the communication interface 710 to send and receive data, and is used to implement the method described in the terminal device in the foregoing method embodiment. Exemplarily, the communication interface 710 is used to receive MCS configuration information, where the MCS configuration information is used to indicate at least one of the following: a first MSC configuration, a second MSC configuration, where the first MSC configuration is a first MCS table The second MSC is configured as an MSC configuration in the second MCS table; the processor 720 is configured to determine the MCS configuration in the supported MCS table according to the MCS configuration information received by the communication module , The MCS table is the first MCS table or the second MCS table. The processor 720 and the communication interface 710 may also be used to perform other corresponding steps or operations performed by the terminal device in the foregoing method embodiment, which will not be repeated here.

The apparatus 700 may further include at least one memory 730 for storing program instructions and/or data. The memory 730 and the processor 720 are coupled. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 720 may operate in cooperation with the memory 730. The processor 720 may execute program instructions stored in the memory 730. At least one of the at least one memory may be included in the processor.

The specific connection medium between the above-mentioned communication interface 710, the processor 720, and the memory 730 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 730, the processor 720, and the communication interface 710 are connected by a bus 740 in FIG. 7. The bus is represented by a thick line in FIG. 7, and the connection mode between other components is only for schematic illustration. , Is not limited. The bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 7, but it does not mean that there is only one bus or one type of bus.

In an embodiment, when the device 600 and the device 700 are specifically chips or chip systems, the information output or received by the communication module 601 and the communication interface 710 may be in the form of baseband signals. For example, when the apparatus 600 and the apparatus 700 implement the functions of the terminal device, the communication module 602 and the communication interface 710 receive the baseband signal that carries the MCS configuration information. The MCS configuration information mentioned in this application is sent by a network device, but it only indicates that the source of the "MCS configuration information" is the network device, but it does not mean that the information must be obtained by the device 600 and the device 700 directly from the network device. That is, the original signal (for example, radio frequency signal) carrying the "MCS configuration information" sent by the network device is processed by other elements or components in the equipment where the devices 600 and 700 are located before being transmitted to the communication interfaces of the devices 600 and 700.

In an embodiment, when the apparatus 600 and the apparatus 700 are specifically devices, the output or reception of the communication module 602 and the communication interface 710 may be radio frequency signals. For example, when the apparatus 600 and the apparatus 700 implement the functions of terminal equipment, the communication module 602 and the communication interface 710 receive radio frequency signals that carry MCS configuration information.

In the embodiments of the present application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, which may implement or Perform the methods, steps, and logical block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.

In the embodiment of the present application, the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), for example Random-access memory (random-access memory, RAM). The memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.

FIG. 8 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device can be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the method embodiments described in FIGS. 4 to 5 above. For ease of description, FIG. 8 only shows the main components of the terminal device. As shown in FIG. 8, the terminal device 80 includes a processor, a memory, a control circuit, an antenna, and an input and output device. The processor is mainly used to process the communication protocol and communication data, and to control the entire terminal device, execute the software program, and process the data of the software program, for example, to support the terminal device to execute the method embodiments described in Figures 4 to 5 above. The actions described in. The memory is mainly used to store software programs and data. The control circuit is mainly used for the conversion of baseband signals and radio frequency signals and the processing of radio frequency signals. The control circuit and the antenna together can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used to receive data input by users and output data to users.

When the terminal device is turned on, the processor can read the software program in the memory, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.

Those skilled in the art can understand that, for ease of description, FIG. 8 only shows one memory and one processor. In an actual terminal device, there may be multiple processors and multiple memories. The memory may also be referred to as a storage medium or storage device. The memory may be a storage element on the same chip as the processor, that is, an on-chip storage element, or an independent storage element, which is not limited in the embodiment of the present application.

As an optional implementation, the terminal device may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire terminal device. , Execute the software program, and process the data of the software program. The processor in FIG. 8 can integrate the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit can also be independent processors and are interconnected by technologies such as a bus. Those skilled in the art can understand that the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and the various components of the terminal device may be connected through various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data can be built in the processor, or can be stored in the memory in the form of a software program, and the processor executes the software program to realize the baseband processing function.

In the embodiment of the present application, the antenna and the control circuit with the transceiving function can be regarded as the transceiving unit 801 of the terminal device 80, for example, to support the terminal device to perform the receiving function and the transmitting function. The processor 802 with processing functions is regarded as the processing unit 802 of the terminal device 80. As shown in FIG. 8, the terminal device 80 includes a transceiver unit 801 and a processing unit 802. The transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, and so on. Optionally, the device for implementing the receiving function in the transceiver unit 801 can be regarded as the receiving unit, and the device for implementing the sending function in the transceiver unit 801 as the sending unit, that is, the transceiver unit 801 includes a receiving unit and a sending unit. The receiving unit may also be called a receiver, an input port, a receiving circuit, etc., and the sending unit may be called a transmitter, a transmitter, or a transmitting circuit, etc.

The processor 802 may be used to execute instructions stored in the memory to control the transceiver unit 801 to receive signals and/or send signals, so as to complete the functions of the terminal device in the foregoing method embodiment. The processor 802 also includes an interface for realizing signal input/output functions. As an implementation manner, the function of the transceiving unit 801 may be implemented by a transceiving circuit or a dedicated chip for transceiving.

FIG. 9 is a schematic structural diagram of a network device provided by an embodiment of the present application, for example, it may be a schematic structural diagram of a base station. As shown in Fig. 9, the network can be applied to the system shown in Fig. 1 to perform the functions of the network device in the method embodiments described in Figs. 4 to 5 above. The base station 90 may include one or more distributed units (DU) 901 and one or more centralized units (CU) 902. The DU 901 may include at least one antenna 9011, at least one radio frequency unit 9012, at least one processor 909, and at least one memory 9014. The DU 901 part is mainly used for the transmission and reception of radio frequency signals, the conversion of radio frequency signals and baseband signals, and part of baseband processing. The CU 902 may include at least one processor 9022 and at least one memory 9021. CU902 and DU901 can communicate through interfaces, where the control plan interface can be Fs-C, such as F1-C, and the user plane (User Plan) interface can be Fs-U, such as F1-U.

The CU 902 part is mainly used to perform baseband processing, control the base station, and so on. The DU 901 and the CU 902 may be physically set together, or may be physically separated, that is, a distributed base station. The CU 902 is the control center of the base station, which may also be referred to as a processing unit, and is mainly used to complete baseband processing functions. For example, the CU 902 may be used to control the base station to execute the operation process of the network device in the method embodiments described in FIGS. 4 to 5 above.

Specifically, the baseband processing on the CU and the DU can be divided according to the protocol layer of the wireless network. For example, the functions of the PDCP layer and the above protocol layers are set in the CU, and the protocol layers below the PDCP, such as the RLC layer and the MAC layer, are set in the DU. . For another example, the CU implements the functions of the RRC and PDCP layers, and the DU implements the functions of the RLC, MAC, and physical (physical, PHY) layers.

In addition, optionally, the base station 90 may include one or more radio frequency units (RU), one or more DUs, and one or more CUs. The DU may include at least one processor 909 and at least one memory 9014, the RU may include at least one antenna 9011 and at least one radio frequency unit 9012, and the CU may include at least one processor 9022 and at least one memory 9021.

In an example, the CU902 can be composed of one or more single boards, and multiple single boards can jointly support a wireless access network (such as a 5G network) with a single access indication, or can respectively support wireless access networks of different access standards. Access network (such as LTE network, 5G network or other networks). The memory 9021 and the processor 9022 may serve one or more boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board. The DU901 can be composed of one or more single boards. Multiple single boards can jointly support a wireless access network with a single access indication (such as a 5G network), and can also support wireless access networks with different access standards (such as LTE network, 5G network or other network). The memory 9014 and the processor 909 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.

The embodiment of the present application also provides a computer-readable medium on which a computer program is stored. When the computer program is executed by a communication device, the communication device realizes the above MCS configuration method.

The embodiments of the present application also provide a computer program product, which when executed by a communication device, enables the communication device to implement the above MCS configuration method.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalent technologies, the present application is also intended to include these modifications and variations.

Claims (28)

1. A modulation and coding scheme MCS configuration method, which is characterized in that it comprises:

   The terminal device receives MCS configuration information, where the MCS configuration information is used to indicate at least one of the following: a first MSC configuration, a second MSC configuration, where the first MSC configuration is an MSC configuration in the first MCS table, so The second MSC configuration is an MSC configuration in the second MCS table;

   The terminal device determines the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information, where the MCS table is the first MCS table or the second MCS table.
2. The method according to claim 1, wherein the MCS configuration information is used to indicate the configuration of the first MSC;

   The terminal device determining the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information includes:

   If the terminal device does not support the first MCS table and the first MSC configuration belongs to the second MCS table, the terminal device determines the MCS index in the second MCS table according to the MCS configuration information, The MCS configuration indicated in the second MCS table by the MCS index is the same as the first MSC configuration;

   The terminal device determines the MCS configuration indicated by the MCS index in the second MCS table according to the MCS index.
3. The method according to claim 2, wherein in the case that the MCS index configured by the first MSC in the first MCS table belongs to the first index set, the MCS configuration indicated by the MCS configuration information Belongs to the second MCS table.
4. The method according to claim 1, wherein the MCS configuration information is used to indicate the configuration of the first MSC;

   The terminal device determining the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information includes:

   If the terminal device does not support the first MCS table and the first MSC configuration does not belong to the second MCS table, the terminal device does not use the MCS configuration indicated by the MCS configuration information.
5. The method according to claim 4, wherein when the MCS index configured by the first MSC in the first MCS table belongs to a first index set, it indicates that the MCS configuration indicated by the MCS configuration information Does not belong to the second MCS table.
6. The method according to any one of claims 2 to 5, wherein the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table.
7. The method of claim 1, wherein the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration;

   The terminal device determining the MCS configuration in the MCS table supported by the terminal device according to the MCS configuration information includes:

   If the terminal device supports the first MCS table, the terminal device determines the first MCS configuration in the first MCS table according to the MCS configuration information; or

   If the terminal device does not support the first MCS table, the terminal device determines the second MCS configuration in the second MCS table according to the MCS configuration information.
8. The method of claim 7, wherein the first MCS configuration is the same as the second MCS configuration.
9. The method according to any one of claims 1 to 8, wherein the MCS configuration information is further used to indicate the value of q in the MCS table, where q is a modulation order, and the value range is 0 or 1. .
10. A modulation and coding scheme MCS configuration method, which is characterized in that it comprises:

    The terminal device receives two physical uplink shared channel PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, the second PUSCH configuration corresponds to the second communication state, and the two PUSCH configurations are used to configure the PUSCH in the two-step random access process Resources;

    The terminal device uses the corresponding PUSCH configuration according to the communication state.
11. The method according to claim 10, wherein the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource have different field lengths.
12. The method according to claim 10 or 11, wherein the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource indicate different content.
13. The method according to any one of claims 10 to 12, wherein the terminal device uses the corresponding PUSCH configuration according to the communication state it is in, comprising:

    Using the first PUSCH configuration when the terminal device is in the first communication state; or

    The terminal device uses the second PUSCH configuration when in the second communication state.
14. A modulation and coding scheme MCS configuration device, which is characterized in that it comprises:

    The communication module is configured to receive MCS configuration information, where the MCS configuration information is used to indicate at least one of the following: a first MSC configuration, a second MSC configuration, where the first MSC is configured as an MSC in the first MCS table Configuration, the second MSC is configured as an MSC configuration in the second MCS table;

    The processing module is configured to determine the MCS configuration in a supported MCS table according to the MCS configuration information received by the communication module, where the MCS table is the first MCS table or the second MCS table.
15. The apparatus according to claim 14, wherein the MCS configuration information is used to indicate the configuration of the first MSC;

    The processing module is specifically used for:

    If the first MCS table is not supported and the first MSC configuration belongs to the second MCS table, the MCS index in the second MCS table is determined according to the MCS configuration information, and the MCS index is in the second MCS table. 2. The MCS configuration indicated in the MCS table is the same as the first MSC configuration;

    Determine the MCS configuration indicated by the MCS index in the second MCS table according to the MCS index.
16. The apparatus according to claim 15, wherein in the case that the MCS index configured by the first MSC in the first MCS table belongs to a first index set, the MCS configuration indicated by the MCS configuration information Belongs to the second MCS table.
17. The apparatus according to claim 14, wherein the MCS configuration information is used to indicate the configuration of the first MSC;

    The processing module is specifically used for:

    If the first MCS table is not supported and the first MSC configuration does not belong to the second MCS table, the MCS configuration indicated by the MCS configuration information is not used.
18. The apparatus according to claim 17, wherein when the MCS index configured by the first MSC in the first MCS table belongs to a first index set, it represents the MCS configuration indicated by the MCS configuration information Does not belong to the second MCS table.
19. The apparatus according to any one of claims 15 to 18, wherein the range indicated by the MCS configuration information is a subset of the MCS configuration in the first MCS table.
20. The apparatus according to claim 14, wherein the MCS configuration information is used to indicate the first MSC configuration and the second MSC configuration;

    The processing module is specifically used for:

    If the first MCS table is supported, determine the first MCS configuration in the first MCS table according to the MCS configuration information; or

    If the first MCS table is not supported, the second MCS configuration is determined in the second MCS table according to the MCS configuration information.
21. The apparatus of claim 20, wherein the first MCS configuration is the same as the second MCS configuration.
22. The device according to any one of claims 14 to 21, wherein the MCS configuration information is further used to indicate the value of q in the MCS table, where q is a modulation order, and the value range is 0 or 1. .
23. A modulation and coding scheme MCS configuration device, which is characterized in that it comprises:

    The communication module is used to receive two physical uplink shared channel PUSCH configurations, where the first PUSCH configuration corresponds to the first communication state, the second PUSCH configuration corresponds to the second communication state, and the two PUSCH configurations are used to configure the two-step random access process PUSCH resources in

    The processing module is used to use the corresponding PUSCH configuration according to the communication state.
24. The apparatus according to claim 23, wherein the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource have different field lengths.
25. The apparatus according to claim 23 or 24, wherein the parameter in the first PUSCH configuration and the parameter in the second PUSCH resource indicate different content.
26. The device according to any one of claims 23 to 25, wherein the processing module is specifically configured to:

    Use the first PUSCH configuration when in the first communication state; or

    The second PUSCH configuration is used when in the second communication state.
27. A computer-readable storage medium, wherein a program or instruction is stored in the computer-readable storage medium, and the program or the instruction can implement claim 1 when read and executed by one or more processors To the method of any one of 13.
28. A computer program product, characterized in that, when the computer program product runs on a terminal device, the terminal device is caused to execute the method according to any one of claims 1 to 13.

Images