A method and apparatus for configuring a modulation and coding scheme

The method allows non-RRC connected UE devices to configure MCS tables for qam64LowSE transmission, addressing the limitation of base stations not knowing UE capabilities, thereby enhancing transmission reliability through reduced signaling overhead.

CN114616860BActive Publication Date: 2025-07-15HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201980101577.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-11-08
Publication Date
2025-07-15
Estimated Expiration
2039-11-08

AI Technical Summary

Technical Problem

In NR systems, UEs in non-RRC connected states cannot use lower spectral efficiency and code rate to obtain higher transmission reliability, resulting in insufficient transmission reliability.

Method used

By default or predefined MCS configuration information, the terminal device determines the MCS configuration based on its own capabilities. The network device does not need to indicate the MCS table additionally, and realizes that the non-RRC connected UE uses the qam64LowSE table to obtain lower spectral efficiency and code rate.

Benefits of technology

It improves the transmission reliability of non-RRC connected UEs, reduces signaling overhead, and avoids PUSCH transmission failure caused by inconsistent MCS configuration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114616860B_ABST
    Figure CN114616860B_ABST
Patent Text Reader

Abstract

The present application discloses an MCS configuration method and apparatus, which can enable a UE in a non-RRC connected state to use a lower spectral efficiency and code rate when supporting qam64LowSE to obtain higher transmission reliability. The method includes: a terminal device receives MCS configuration information, and determines an MCS configuration in an MCS table supported by the terminal device according to the MCS configuration information. Wherein, the MCS configuration information is used to indicate at least one of the following: the MCS configuration in a first MCS table, the MCS configuration in a second MCS table. By defaulting or configuring or predefining the table used for the MCS configuration information in the present application, the network device does not need to additionally configure indication information to indicate which MCS table to use, thereby saving signaling overhead. And the network device can configure the MCS configuration in the MCS table corresponding to qam64LowSE without knowing the terminal capabilities, so that the terminal device supporting qam64LowSE can use a lower spectral efficiency and code rate to obtain higher transmission reliability.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communication technologies, and particularly to a method and device for configuring a modulation and coding scheme (MCS). Background Art

[0002] In a new radio (NR) system, there are two waveforms for the physical uplink shared channel (PUSCH). Under each waveform, there are 3 MCS tables for determining the MCS, namely: the qam256 table, the qam64LowSE table, and the qam64 table. Among them, the highest modulation order supported by the qam256 table is 8, the highest modulation orders supported by the qam64 table and the qam64LowSE table are both 6, and the qam64LowSE table can support lower spectral efficiency and code rate.

[0003] 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 obtain the capabilities of UEs in the radio resource control (RRC) connected state. Therefore, for UEs in the RRC connected state, the base station can indicate the MCS table that the UE can use when sending PUSCH according to the UE's capabilities. However, for UEs in the non-connected state, even if the UE supports the qam64LowSE table, the base station can only configure the UE to use the qam64 table to send PUSCH, and cannot use lower spectral efficiency and code rate to obtain higher transmission reliability. Summary of the Invention

[0004] This application provides an MCS configuration method and device, which can enable UEs in the non-RRC connected state to use lower spectral efficiency and code rate to obtain higher transmission reliability when supporting the qam64LowSE table.

[0005] In a first aspect, an MCS configuration method provided by an embodiment of the present application includes: a terminal device receives MCS configuration information and determines an MCS configuration in an MCS table supported by the terminal device according to the MCS configuration information. Among them, the MCS configuration information is used to indicate at least one of the following: a first MCS configuration and a second MCS configuration, where the first MCS configuration is an MCS configuration in a first MCS table, and the second MCS configuration is an MCS configuration in a second MCS table. In the embodiment of the present application, by default or configuration or predefined table used for MCS configuration information, thus, the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, and the terminal device can determine the MCS configuration according to its own capabilities and the MCS configuration information, thereby saving signaling overhead. Moreover, 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 spectral efficiency and coding rate to obtain higher transmission reliability.

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

[0007] In a possible design, the MCS configuration information is used to indicate the first MCS configuration. In the above design, by default or protocol stipulation, the qam64LowSE table is used for the MCS configuration information, and the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. Moreover, 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 spectral efficiency and coding rate to obtain higher transmission reliability.

[0008] 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 MCS configuration belongs to the second MCS table, the terminal device can determine the MCS index in the second MCS table according to the MCS configuration information, and the MCS configuration indicated by the MCS index in the second MCS table is the same as the first MCS 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, the terminal device that does not support the qam64LowSE table can use the MCS configuration of the qam64 table. Moreover, the MCS configuration determined through 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 different MCS configurations between the network device and the terminal device.

[0009] In a possible design, when the MCS index of the first MCS configuration 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.

[0010] In a possible design, when the terminal device determines the MCS configuration in the MCS tables 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 MCS configuration does not belong to the second MCS table, the terminal device may not use the MCS configuration indicated by the MCS configuration information, 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 gives up using the MCS configuration indicated by the MCS configuration information, which can avoid the problem of PUSCH transmission failure caused by different MCS configurations between the network device and the terminal device.

[0011] In a possible design, when the MCS index of the first MCS configuration 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.

[0012] In a possible design, the range indicated by the MCS configuration information is a subset of the MCS configurations in the first MCS table. In the above design, by indicating a subset of the MCS configuration through the MCS configuration information, the signaling overhead can be reduced.

[0013] In a possible design, when the terminal device determines the MCS configuration in the MCS tables 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 MCS configuration in the first MCS table. Through the above design, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, enabling the terminal device supporting the qam64LowSE table to use lower spectral efficiency and coding rate to obtain higher transmission reliability.

[0014] In a possible design, when the terminal device selects the MCS configuration in the MCS tables 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 MCS configuration. Through the above design, when the qam64LowSE table is not supported, the terminal device gives up using the MCS configuration indicated by the MCS configuration information, which can avoid the problem of PUSCH transmission failure caused by different MCS configurations between the network device and the terminal device.

[0015] In a possible design, the MCS configuration information is used to indicate a first MCS configuration and a second MCS configuration. In the above design, by default or as stipulated by the protocol, the MCS configuration information uses the qam64LowSE table and the qam64 table. The network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, thus saving signaling overhead. Moreover, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, enabling terminal devices that support the qam64LowSE table to use lower spectral efficiency and coding rate to obtain higher transmission reliability.

[0016] 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 MCS configuration in the first MCS table according to the MCS configuration information. In the above design, the network device can configure the MCS configuration of the qam64LowSE table without knowing the terminal capabilities, enabling terminal devices that support the qam64LowSE table to use lower spectral efficiency and coding rate to obtain higher transmission reliability.

[0017] 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 determines the second MCS configuration in the second MCS table according to the MCS configuration information. Through the above design, terminal devices that do not support the qam64LowSE table can use the MCS configuration of the qam64 table.

[0018] In a possible design, the first MCS configuration is the same as the second MCS configuration. Through the above design, regardless of whether the terminal device supports the MCS configuration determined by the qam64LowSE table, the MCS configuration is the same, so that the MCS configuration of the network device and the terminal device is the same, thus avoiding the problem of PUSCH transmission failure caused by different MCS configurations between the network device and the terminal device.

[0019] 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 device does not need to additionally configure the RRC parameter tp-pi2BPSK to determine the value of q, and the terminal device can determine the value of q according to the MCS configuration information, thus saving signaling overhead.

[0020] Second aspect, an MCS configuration method provided by an embodiment of the present application, the method includes: a network device sending MCS configuration information. The MCS configuration information is used to indicate at least one of the following: a first MCS configuration, a second MCS configuration, where the first MCS configuration is an MCS configuration in a first MCS table, and the second MCS configuration is an MCS configuration in a second MCS table. In the embodiment of the present application, by default or configuration or predefined table for using the MCS configuration information, thus, the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, and the terminal device can determine the MCS configuration according to its own capabilities and the MCS configuration information, thereby saving signaling overhead. Moreover, 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 spectral efficiency and code rate to obtain higher transmission reliability.

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

[0022] In a possible design, the MCS configuration information is used to indicate the first MCS configuration. In the above design, by default or protocol stipulation that the MCS configuration information uses the qam64LowSE table, the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. Moreover, 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 spectral efficiency and code rate to obtain higher transmission reliability.

[0023] In a possible design, the range indicated by the MCS configuration information is a subset of the MCS configurations in the first MCS table. In the above design, by the way that the MCS configuration information indicates a subset of the MCS configurations, the signaling overhead can be reduced.

[0024] In a possible design, the MCS configuration information is used to indicate the first MCS configuration and the second MCS configuration. In the above design, by default or protocol stipulation that the MCS configuration information uses the qam64LowSE table and the qam64 table, the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, thereby saving signaling overhead. Moreover, 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 spectral efficiency and code rate to obtain higher transmission reliability.

[0025] In a possible design, the first MCS configuration is the same as the second MCS configuration. With the above design, regardless of whether the terminal device supports it or not, the MCS configuration determined by the qam64LowSE table is the same, so that the MCS configuration of the network device and the terminal device is the same, thereby avoiding the problem of PUSCH transmission failure caused by different MCS configurations between the network device and the terminal device.

[0026] 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. With the above design, the network device does not need to additionally configure the RRC parameter tp-pi2BPSK to determine the value of q, and the terminal device can determine the value of q according to the MCS configuration information, thereby saving signaling overhead.

[0027] In a third aspect, a method for configuring MCS provided in an embodiment of the present application includes: a terminal device receives two PUSCH configurations, where the first PUSCH configuration corresponds to a first communication state and the second PUSCH configuration corresponds to a second communication state, and the two PUSCH configurations are used to configure PUSCH resources in a two-step random access process; the terminal device uses the corresponding PUSCH configuration according to the communication state it is in. In the embodiment of the present application, for different communication states, according to the service type and service size, different value ranges and / or indicated contents of the same resource configuration parameters can be used to more flexibly configure resources for different communication states.

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

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

[0030] In a possible design, the first communication state may be communication in authorized spectrum, and the second communication state may be communication in unlicensed spectrum.

[0031] In a possible design, the first communication state may be communication in unlicensed spectrum, and the second communication state may be communication in authorized spectrum.

[0032] In a possible design, the field lengths of the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource may be different. In the above design, for different communication states, different value ranges of the same resource configuration parameters can be used to more flexibly configure resources for different communication states.

[0033] In a possible design, the parameters in the first PUSCH configuration may have different indicated contents from those in the second PUSCH resource. In the above design, for different communication states, using different indicated contents for the same resource configuration parameters can configure the resources of different communication states more flexibly.

[0034] 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.

[0035] 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.

[0036] In a fourth aspect, an MCS configuration method provided by an embodiment of the present application includes: The 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. The two PUSCH configurations are used to configure the PUSCH resources in the two-step random access procedure. In the embodiment of the present application, for different communication states, according to the service type and service size, using different value ranges and / or indicated contents for the same resource configuration parameters can configure the resources of different communication states more flexibly.

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

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

[0039] In a possible design, the first communication state may be to communicate in the authorized spectrum, and the second communication state may be to communicate in the unlicensed spectrum.

[0040] In a possible design, the first communication state may be to communicate in the unlicensed spectrum, and the second communication state may be to communicate in the authorized spectrum.

[0041] In a possible design, the field lengths of the parameters in the first PUSCH configuration and the parameters 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 configure the resources of different communication states more flexibly.

[0042] In a possible design, the parameters in the first PUSCH configuration may be different from the content indicated by the parameters in the second PUSCH resource. In the above design, for different communication states, using different indication contents for the same resource configuration parameters can more flexibly configure the resources for different communication states.

[0043] In a fifth aspect, the present application provides an MCS configuration device, which may be a communication device, or a chip or chipset within a communication device. Among them, the communication device may be a terminal device or a network device. The device may include a processing unit and a transceiver unit. When the device is a communication device, the processing unit may be a processor, and the transceiver unit may be a transceiver; the device may further include a storage module, and the storage module may be a memory; the storage module is used to store instructions, and the processing unit executes the instructions stored in the storage module, so that the terminal device executes the corresponding functions in the first aspect or the third aspect above, or so that the network device executes the corresponding functions in the second aspect or the fourth aspect above. When the device is a chip or chipset within a communication device, the processing unit may be a processor, and the transceiver unit may be an input / output interface, a pin, a circuit, etc.; the processing unit executes the instructions stored in the storage module, so that the terminal device executes the corresponding functions in the first aspect or the third aspect above, or so that the network device executes the corresponding functions in the second aspect or the fourth aspect above. The storage module may be a storage module within the chip or chipset (for example, a register, a cache, etc.), or may be a storage module outside the chip or chipset within the communication device (for example, a read-only memory, a random access memory, etc.).

[0044] In a sixth aspect, an MCS configuration device is provided, including: a processor, a communication interface, and a memory. The communication interface is used for the device to transmit information, and / or messages, and / or data to and from other devices. The memory is used to store computer execution instructions. When the device runs, the processor executes the computer execution instructions stored in the memory, so that the device executes the MCS configuration method described in the first aspect or any design in the first aspect, or the third aspect or any design in the third aspect above.

[0045] In a seventh aspect, an MCS configuration device is provided, including: a processor, a communication interface, and a memory. The communication interface is used for the device to transmit information, and / or messages, and / or data to and from other devices. The memory is used to store computer execution instructions. When the device runs, the processor executes the computer execution instructions stored in the memory, so that the device executes the MCS configuration method described in the second aspect or any design in the second aspect, or the fourth aspect or any design in the fourth aspect above.

[0046] In an eighth aspect, a computer storage medium provided by an embodiment of the present application stores program instructions. When the program instructions are run on a terminal device, the terminal device is caused to execute the methods of the first aspect and any possible design thereof, or the second aspect or any design in the second aspect, or the third aspect or any design in the third aspect, or the fourth aspect or any design in the fourth aspect of the embodiments of the present application.

[0047] In a ninth aspect, a computer program product provided by an embodiment of the present application, when run on a terminal device, causes the terminal device to execute the methods of the first aspect and any possible design thereof, or the second aspect or any design in the second aspect, or the third aspect or any design in the third aspect, or the fourth aspect or any design in the fourth aspect of the embodiments of the present application.

[0048] In a tenth aspect, a chip provided by an embodiment of the present application is coupled to a memory and executes the methods of the first aspect and any possible design thereof, or the third aspect or any design in the third aspect of the embodiments of the present application.

[0049] In an eleventh aspect, a chip provided by an embodiment of the present application is coupled to a memory and executes the methods of the second aspect and any possible design thereof, or the third aspect or any design in the third aspect of the embodiments of the present application.

[0050] In addition, for the technical effects brought by the fifth aspect to the eleventh aspect, reference may be made to the descriptions of the first aspect to the fourth aspect above, which will not be elaborated here.

[0051] It should be noted that "coupling" in the embodiments of the present application means that two components are directly or indirectly combined with each other. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application;

[0053] Figure 2 is a schematic flowchart of a four-step random access provided by an embodiment of the present application;

[0054] Figure 3 is a schematic flowchart of a two-step random access provided by an embodiment of the present application;

[0055] Figure 4 is a schematic flowchart of a method for configuring MCS provided by an embodiment of the present application;

[0056] Figure 5 is a schematic flowchart of another method for configuring MCS provided by an embodiment of the present application;

[0057] Figure 6Schematic structural diagram of a communication device provided by an embodiment of the present application;

[0058] Figure 7 Schematic structural diagram of another communication device provided by an embodiment of the present application;

[0059] Figure 8 Schematic structural diagram of a terminal device provided by an embodiment of the present application;

[0060] Figure 9 Schematic structural diagram of a base station provided by an embodiment of the present application. Detailed implementation manners

[0061] The MCS configuration method provided by the present application can be applied to various communication systems. For example, it can be an Internet of Things (IoT) system, a Narrow Band Internet of Things (NB-IoT) system, a Long Term Evolution (LTE) system, or a fifth-generation (5G) communication system. It can also be an LTE and 5G hybrid architecture, a 5G NR system, and new communication systems emerging in the future development of communications, etc.

[0062] 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 can be a device that provides voice and / or data connectivity to users. For example, it can be a handheld device with wireless connection capabilities, a vehicle-mounted device, etc. The terminal device can also be other processing devices connected to a wireless modem. The terminal device can communicate with a radio access network (RAN). The terminal device can also be referred to as a wireless terminal, subscriber unit, subscriber station, mobile station, mobile, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment (UE), etc. The terminal device can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges voice and / or data with the wireless access network. For example, the terminal device can also be a personal communication service (PCS) phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc. Common terminal devices include, for example: mobile phones, tablet computers, laptop computers, palmtop computers, mobile internet devices (MIDs), wearable devices, such as smart watches, smart bracelets, pedometers, etc., but the embodiments of the present application are not limited thereto.

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

[0064] The method for determining random access resources provided by the embodiments of this application can be applied to Figure 1 the communication system shown in the figure, where the network device and UE1 - UE3 form a single-cell communication system, and UE1 - UE3 can send uplink data to the network device separately or simultaneously, and the network device can send downlink data to UE1 - UE3 separately or simultaneously. It should be understood that Figure 1 this is only an exemplary illustration and does not specifically limit the number of terminal devices and network devices included in the communication system or the number of cells covered by the network device.

[0065] The network architecture and service scenarios described in the embodiments of this application are for more clearly explaining the technical solutions of the embodiments of this application and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of this application are equally applicable to similar technical problems.

[0066] In wireless communication systems such as LTE, 5G, and NR, a UE can enter the RRC connected state from the RRC idle state or inactive state through random access, establish various bearers with the network device, obtain some necessary resources and parameter configurations, and then communicate with the network device.

[0067] Currently, in wireless communication systems such as LTE and 5G NR, a UE usually needs four steps to perform random access, as Figure 2 shown in the figure:

[0068] In S201, the UE sends a random access preamble to the network device, which can also be referred to as the first message (Msg1). The role of the random access preamble is to notify the network device of 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 inform the UE of the calibration information through a timing advance command.

[0069] In S202, after detecting the random access preamble, the network device sends a random access response to the UE, which can also be referred to as the second message (Msg2). The random access response can, but is not limited to, include the sequence number of the random access preamble received in S201, the timing advance command, the uplink resource allocation information, and the cell radio network temporary identifier, etc.

[0070] In S203, the UE receives the 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, the UE considers that the random access response is the random access response for this UE, that is, the UE has received its own random access response. 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, it sends a PUSCH in Msg3, which is also referred to as the third message (Msg3). Among them, Msg3 can carry a unique user identifier.

[0071] In S204, after receiving the UE's uplink message, the network device returns a conflict resolution message to the UE that has successfully accessed, which is also referred to as the 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.

[0072] For the four-step random access procedure, when a UE in the idle state or inactive state wants to perform uplink data transmission, it must first complete the above four information exchanges to enter the RRC connected state. For ultra-reliable and low latency communications (URLLC) services, the four information exchanges will generate relatively high latency, which is not conducive to the low latency requirements of URLLC. For massive machine type communications (mMTC) services, since most services are sporadic small packets, the UE needs to complete a full four-step random access to enter the RRC connected state every time to send data once, and then return to the idle state or inactive state again. This not only results in relatively high latency, but also causes serious signaling overhead.

[0073] To reduce the access latency and signaling overhead, a two-step random access procedure has been proposed currently, as Figure 3 shown. In this procedure, in the first step, the UE simultaneously sends a random access preamble and data to the network device. In the second step, the network device sends a random access response to the UE. In the two-step random access procedure, on the one hand, the UE sends the random access preamble and data simultaneously in the first step, thus greatly reducing the latency 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, thereby reducing the signaling overhead. Usually, MsgA can be used to represent the first interaction message of the two-step random access. MsgA is sent from the UE to the network device. The MsgA message includes a MsgA preamble part and a MsgA data part. The preamble is transmitted on the physical random access channel (PRACH) of the MsgA physical channel, and the data part is transmitted on the MsgA PUSCH physical channel. For the convenience of description, without affecting the understanding of the context, hereinafter, "preamble" is used to refer to the "MsgA preamble part", "data" is used to refer to the "MsgA data part", "PRACH" is used to refer to the "MsgA PRACH physical channel", and "PUSCH" is used to refer to the "MsgA PUSCH physical channel".

[0074] In the NR system, there are two waveforms for PUSCH. When the transform precoder is activated, it is the discrete fourier transform-spread OFDM (DFT-s-OFDM) waveform, and when the transform precoder is not activated, it is the Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform. Under each waveform, there are 3 MCS tables for determining the MCS. The three MCS tables for the CP-OFDM waveform are Table 5.1.3.1-1 (corresponding to qam64), Table 5.1.3.1-2 (corresponding to qam256), and Table 5.1.3.1-3 (corresponding to qam64LowSE) in Protocol TS38.214 respectively. The three MCS tables for 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 qam64LowSE) in Protocol TS38.214 respectively. Among them, the highest modulation order supported by qam256 is 8, the highest modulation orders supported by qam64LowSE and qam64 are 6, and qam64LowSE can support lower spectral efficiency and code rate. Exemplarily, the MCS table corresponding to qam64 when the transform precoder is not activated can be as shown in Table 1. Among them, I MCS is the MCS Index (MCS Index). Q m is the Modulation Order (ModulationOrder). R x

[1024] is the Target code Rate (Target code Rate).

[0075] Table 1

[0076]

[0077]

[0078] Exemplarily, the MCS table corresponding to qam64LowSE when the transform precoder is not activated can be as shown in Table 2.

[0079] Table 2

[0080]

[0081]

[0082] Exemplarily, the MCS table corresponding to qam64 when the transform precoder is activated can be as shown in Table 3.

[0083] Table 3

[0084]

[0085]

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

[0087] Table 4

[0088]

[0089]

[0090] When the terminal device is in the RRC connected state, the base station indicates which MCS table to use for the PUSCH to determine the MCS through RRC parameters respectively. For example, the base station can indicate which MCS table to use for the PUSCH of the CP-OFDM waveform to determine the MCS configuration through the mcs-Table parameter. 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 as "qam64LowSE", the PUSCH of the CP-OFDM waveform uses the MCS table corresponding to qam64LowSE (as shown in Table 2) to determine the MCS configuration. Another example is that the base station can indicate which MCS table to use for the PUSCH of the DFT-s-OFDM waveform to determine the MCS through the mcs-TableTransformPrecoder parameter. For example, when the mcs-TableTransformPrecoder parameter is configured as "qam256", the PUSCH of the DFT-s-OFDM waveform uses the MCS table corresponding to qam256 to determine the MCS configuration, and when the mcs-TableTransformPrecoder parameter is configured as "qam64LowSE", the PUSCH of the DFT-s-OFDM waveform uses the MCS table corresponding to qam64LowSE (as shown in Table 4) to determine the MCS configuration.

[0091] The base station can also indicate the use of the qam64LowSE table through the MCS - cell radio network temporary identity (MCS - C - RNTI). For example, when the base station configures the MCS - C - RNTI for the UE and indicates that the UE uses this MCS - C - RNTI to schedule the PUSCH, the UE determines the MCS configuration using the MCS table corresponding to qam64LowSE. If the base station does not configure the mcs - Table and mcs - TableTransformPrecoder and does not use the MCS - C - RNTI to schedule the PUSCH, the UE can default to using the MCS table corresponding to qam64.

[0092] Since qam256 and qam64LowSE are optional user equipment (UE) capabilities, not all UEs support qam256 and qam64LowSE. The base station can only obtain the capabilities of UEs in the radio resource control (RRC) connected state. Therefore, for UEs in the RRC connected state, the base station can indicate the MCS table that the UE can use when sending the PUSCH according to the UE's capabilities. However, for UEs in the non - connected state, even if the UE supports qam64LowSE, the base station can only configure the UE to send the PUSCH using the MCS in the MCS table corresponding to qam64 and cannot use a lower spectral efficiency and code rate to obtain higher transmission reliability.

[0093] Based on this, the embodiments of the present application provide an MCS configuration method and apparatus, which can implement the configuration of the qam64LowSE table for terminal devices in the non - RRC connected state. Thus, when the terminal device in the non - RRC connected state supports the qam64LowSE table, it can determine the MCS configuration according to the qam64LowSE table, and further can use a lower spectral efficiency and code rate to obtain higher transmission reliability. Among them, the method and the apparatus are based on the same inventive concept. Since the principles of the method and the apparatus for solving problems are similar, the implementation of the apparatus and the method can be referred to each other, and the repeated parts will not be elaborated.

[0094] It should be understood that in the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item) of the following" or its similar expression refers to any combination of these items, including any combination of single item (s) or plural items (s). For example, at least one (item) of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple. In addition, it should be understood that in the description of the present application, terms such as "first", "second", and "third" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0095] Next, the embodiments of the present application will be described in detail with reference to the accompanying drawings.

[0096] Embodiment 1:

[0097] As Figure 4 shown, a method for configuring MCS provided by an embodiment of the present application can be applied to Figure 1 the communication system shown. Specifically, this method can be applied to a terminal device. The method for configuring MCS can specifically include:

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

[0099] 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 Table 5.1.3.1-3 in Protocol TS38.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 referred to as the MCS table corresponding to qam64, or may also be referred to as the qam64 table. Or the first MCS table may refer to Table 5.1.3.1-1 in Protocol TS38.214 or Table 6.1.4.1-1 in Protocol TS38.214. For the convenience of description, hereinafter the first MCS table will be uniformly referred to as the "qam64LowSE table", and the second MCS table will be uniformly referred to as the "qam64 table".

[0100] It should be understood that the qam64LowSE table and the qam64 table are only exemplary names. In specific implementations or future communication developments, they may also be named otherwise. For example, the qam64LowSE table may also be named A, and the qam64 table may 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 embodiments of the present application, and B can be understood as the qam64 table in the embodiments of the present application.

[0101] S402. The terminal device determines the MCS configuration in the MCS tables supported by the terminal device according to the MCS configuration information, and the MCS table is the qam64LowSE table or the qam64 table.

[0102] Furthermore, the terminal device can also determine the PUSCH resource configuration corresponding to the MCS configuration.

[0103] The following introduces three exemplary descriptions of the MCS configuration information.

[0104] In the first exemplary description, for each PUSCH waveform, one MCS table can be used by default or predefined by the protocol. For example, using the qam64LowSE table by default or predefined by the protocol can be understood as the MCS configuration information by default or predefined by the protocol indicating an MCS configuration in the qam64LowSE table. Another example, using the qam64 table by default or predefined by the protocol can be understood as the MCS configuration information by default or predefined by the protocol indicating an MCS configuration in the qam64 table.

[0105] The MCS configuration information may be an MCS index, i.e., IMCS. For example, by default or as pre-defined by the protocol, the qam64LowSE table is used, and the MCS configuration information may be the MCS index in the qam64LowSE table. For example, by default or as pre-defined by the protocol, the qam64 table is used, and the MCS configuration information may be the MCS index in the qam64 table.

[0106] Taking the case where the default or protocol-predefined MCS configuration information indicates an MCS configuration in the qam64LowSE table as an example, the following describes step S402 in combination with the first exemplary description.

[0107] In a possible implementation, 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 where the first MCS configuration belongs to the qam64 table, the terminal device may determine the MCS index in the qam64 table according to the MCS configuration information. The MCS configuration indicated by the MCS index in the qam64 table is the same as the first MCS configuration, and then the MCS configuration indicated by the MCS index is determined in the qam64 table according to the MCS index.

[0108] In some embodiments, when the terminal device determines the MCS index in the qam64 table according to the MCS configuration information, it may determine the MCS index 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. Taking Table 1 and Table 2 above as an example, the MCS configuration with index 0 in Table 1 is the same as the MCS configuration with index 6 in Table 2, the MCS configuration with index 1 in Table 1 is the same as the MCS configuration with index 7 in Table 2, the MCS configuration with index 2 in Table 1 is the same as the MCS configuration with index 8 in Table 2, the MCS configuration with index 3 in Table 1 is the same as the MCS configuration with index 9 in Table 2,..., the MCS configuration with index 8 in Table 1 is the same as the MCS configuration with index 14 in Table 2. Thus, if the MCS configuration information is the MCS index 6 in the qam64LowSE table, it can be determined that the corresponding MCS index in 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 corresponding MCS index in 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 corresponding MCS index in 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 corresponding MCS index in the qam64 table is 8.

[0109] Exemplarily, the correspondence between the MCS indexes in the qam64LowSE table and the MCS indexes in the qam64 table can be that the MCS index i in the qam64LowSE table corresponds to the MCS index i - 6 in the qam64 table.

[0110] In another possible implementation, when the terminal device determines the MCS configuration according to the MCS configuration information in the MCS table supported by the terminal device, if the terminal device does not support the qam64LowSE table but the terminal device stores the qam64LowSE table, the terminal device can determine whether the MCS configuration indicated by the MCS configuration information belongs to the qam64 table according to the qam64LowSE 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 where the first MCS configuration belongs to the qam64 table, the terminal device can determine the MCS configuration information indicated by the MCS configuration information according to the stored qam64LowSE table.

[0111] In yet another possible implementation, when the terminal device determines the MCS configuration according to the MCS configuration information in the MCS table supported by the terminal device, if the terminal device does not support the qam64LowSE table, and in the case where the first MCS configuration does not belong to the qam64 table, the terminal device may not use the MCS configuration indicated by the MCS configuration information, or the terminal device does not use the PUSCH configuration associated with the MCS configuration information.

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

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

[0114] Exemplarily, a method for determining whether the first MCS configuration belongs to the qam64 table can be that in the case where the MCS index of the first MCS configuration in the qam64LowSE table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to the qam64 table. Otherwise, the MCS configuration indicated by the MCS configuration information does not belong to the qam64 table.

[0115] 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 that when the MCS configuration information belongs to the first index set, 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 MCS configuration with index 8 in the qam64LowSE table belongs to the qam64 table, which can also be understood as the MCS configuration with index 8 in the qam64LowSE table also exists in the qam64 table.

[0116] Alternatively, another method for determining whether the first MCS configuration belongs to the qam64 table may be that when the MCS index of the first MCS configuration 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. Conversely, 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, the MCS configuration with index 4 in the qam64LowSE table does not belong to the qam64 table, which can also be understood as the qam64 table does not include the MCS configuration with index 4 in the qam64LowSE table.

[0117] Alternatively, yet another method for determining whether the first MCS configuration belongs to the qam64 table may be that when the MCS index of the first MCS configuration in the qam64LowSE table belongs to the first index set, the MCS configuration indicated by the MCS configuration information belongs to the qam64 table. When the MCS index of the first MCS configuration 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.

[0118] In one implementation, the range indicated by the MCS configuration information can be the entire set of MCS configurations in the qam64LowSE table, or a subset of the MCS configurations in the qam64LowSE table. For example, each MCS table has 32 MCSs. If the MCS configuration information is 5 bits, it can indicate any one of the 32 MCS configurations. Alternatively, the MCS configuration information can be less than 5 bits, and it can indicate an MCS configuration from a subset of the 32 MCS configurations. This subset can be predefined or configured by the network device. For example, if the MCS configuration information is 4 bits, the MCS subset is 16 MCS configurations in the MCS table. These 16 MCS configurations can be the first 16 items, the last 16 items, or 16 predefined items in the MCS table. By indicating a subset of the MCS configurations through the MCS configuration information, the signaling overhead can be reduced.

[0119] For example, taking the case where PUSCH transform precoding is not activated, that is, the CP-OFDM waveform as an example, the MCS configuration information can be 4 bits and can indicate one MCS configuration from the first 16 MCS configurations in the qam64LowSE table.

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

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

[0122] Alternatively, the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table can also include an MCS configuration that belongs to the qam64LowSE table and an MCS configuration that belongs to the qam64 table, that is, the MCS configuration information indicates the first MCS configuration and the second MCS configuration. Here, the first MCS configuration and the second MCS configuration can be the same or different, and no specific limitation is made here. Among them, when the first MCS configuration and the second MCS configuration are the same, it can be understood that the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table can also include MCS configurations that belong to both the qam64LowSE table and the qam64 table.

[0123] Alternatively, the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table can also include MCS configurations that belong to the qam64 table but not to the qam64LowSE table, that is, the MCS configuration information only indicates the second MCS configuration.

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

[0125] Table 5

[0126]

[0127] In the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table, it may include MCS configurations that belong to the qam64LowSE table but not to the qam64 table. That is, when the MCS configuration information only indicates the first MCS configuration, such as MCS configuration information 0, MCS configuration information 1, and MCS configuration information 2 in Table 5, the manner in which the terminal device determines the MCS configuration in the MCS tables supported by the terminal device according to the MCS configuration information may specifically refer to the relevant description in the above first exemplary description, which will not be repeated here.

[0128] In the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table, it may also include one MCS configuration belonging to the qam64LowSE table and one MCS configuration belonging to the qam64 table. That is, when the MCS configuration information indicates the first MCS configuration and the second MCS configuration, such as MCS configuration information 3, MCS configuration information 4, MCS configuration information 5, MCS configuration information 6, and MCS configuration information 7 in Table 5. When the terminal device determines the MCS configuration in the MCS tables supported by the terminal device according to the MCS configuration information, if the terminal device supports the qam64LowSE table, the terminal device may determine the first MCS configuration in the qam64LowSE table according to the MCS configuration. If the terminal device does not support the qam64LowSE table, the terminal device may determine the second MCS configuration in the qam64 table according to the MCS configuration.

[0129] For example, assume 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 may use the MCS configuration with an MCS index of 8 in the qam64LowSE table. If the terminal device does not support the qam64LowSE table, the terminal device may use the MCS configuration with an MCS index of 2 in the qam64 table.

[0130] In the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table, it may further include MCS configurations that belong to the qam64 table but not to the qam64LowSE table. That is, when the MCS configuration information only indicates the second MCS configuration, for example, MCS configuration information 8 and MCS configuration information 9 in Table 5. When the terminal device determines the MCS configuration in the MCS tables supported by the terminal device according to the MCS configuration information, the terminal device may determine the second MCS configuration according to the MCS configuration in the qam64 table.

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

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

[0133] Exemplarily, when the terminal device supports the qam64LowSE table, the MCS configuration information i may correspond to the MCS configuration with the MCS index of 2*i in the qam64LowSE table. When the terminal device does not support the qam64LowSE table, the MCS configuration information i may correspond to the MCS configuration with the MCS index of 2*(i - 3) in the qam64 table.

[0134] In the embodiments of the present application, by using a table through default or configuration or predefined MCS configuration information, thus, the network device does not need to additionally configure MCS table indication information to indicate which MCS table to use, and the terminal device can determine the MCS configuration according to its own capabilities and the MCS configuration information, thereby saving signaling overhead. Moreover, 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 spectral efficiency and code rate to obtain higher transmission reliability.

[0135] When PUSCH transform precoding is activated, that is, for DFT-s-OFDM waveform PUSCH, the modulation order of some MCS configurations in the MCS table is the parameter q, such as the modulation order of the MCS configuration with I MCS being 0 in Table 3, the modulation order of the MCS configuration with I MCS being 1 in Table 4, the modulation order of the MCS configuration with I MCS being 0, the modulation order of the MCS configuration with I MCS being 1, the modulation order of the MCS configuration with I MCS being 2, etc. Among them, q = 1 represents pi / 2 binary phase shift keying (BPSK), and q = 2 represents quadrature phase shift keying (QPSK).

[0136] 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 in the modulation order of this MCS configuration. Regarding the value of the parameter q, one possible implementation is to default the value of q. For example, the value of q can be defaulted to 1, that is, it represents pi / 2 BPSK, or the value of q can be defaulted to 2, that is, it represents QPSK.

[0137] Another possible implementation is to determine the value of q according to the RRC parameter tp-pi2BPSK sent by the network device. When tp-pi2BPSK is activated, q = 1, that is, it represents pi / 2 BPSK, and when tp-pi2BPSK is not activated, q = 2, that is, it represents QPSK.

[0138] Yet another possible implementation is to indicate the value of q through the MCS configuration information. For example, the MCS configurations with the parameter q in the modulation order are indicated by two MCS configuration information respectively, that is, one MCS configuration information indicates this MCS configuration and q takes the value of 1, and the other MCS configuration information indicates this MCS configuration and q takes the value of 2.

[0139] For example, taking the QAM64 table of the DFT-s-OFDM waveform as an example in Table 3, there is a parameter q in the first two MCS configurations. If the MCS configuration information is 4 bits, when the MCS configuration information is i (0 ≤ i ≤ 1), it indicates the MCS configuration with the MCS index i in the QAM64 table and q = 2. When the MCS configuration information is i (2 ≤ i ≤ 9), it indicates the MCS configuration with the MCS index i in the QAM64 table. When the MCS configuration information is i (10 ≤ i ≤ 11), it indicates the MCS with the MCS index i - 10 in the QAM64 table and q = 1. The MCS configuration information i (12 ≤ i ≤ 15) can be a reserved item.

[0140] Another example is that the value of the parameter q can be included in the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table in the second exemplary description. For example, the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table may include MCS configurations that belong to the qam64LowSE table but not to the qam64 table and q takes the value of 1, or may also include MCS configurations that belong to the qam64LowSE table but not to the qam64 table and q takes the value of 2.

[0141] Or, the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table may further include an MCS configuration that belongs to the qam64LowSE table, an MCS configuration that belongs to the qam64 table, and the value of q for each MCS configuration.

[0142] Or, the correspondence between the MCS configuration information and at least one MCS configuration in at least one MCS table may further include MCS configurations that belong to the qam64 table but not to the qam64LowSE table and q takes the value of 1, or may also include MCS configurations that belong to the qam64 table but not to the qam64LowSE table and q takes the value of 2.

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

[0144] Table 6

[0145]

[0146]

[0147] In the above manner, the network device does not need to additionally configure the RRC parameter tp-pi2BPSK to determine the value of q, and the terminal device can determine the value of q according to the MCS configuration information, thereby saving signaling overhead.

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

[0149] In one implementation, 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 3 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 according to the first MCS configuration information, the MCS configuration may be used. If it is determined not to use the MCS configuration indicated by the first MCS configuration information, the MCS configuration may be determined in the MCS table supported by the terminal device according to the second MCS configuration information. If the MCS configuration is determined according to the second MCS configuration information, the MCS configuration may be used. If it is determined not to use the MCS configuration indicated by the second MCS configuration information, the MCS configuration may be determined in the MCS table supported by the terminal device according to the third MCS configuration information.

[0150] In another implementation, the terminal device may separately determine the MCS configuration in the MCS table supported by the terminal device according to multiple MCS configuration information, so that the terminal device may select one MCS configuration from the determined MCS configurations according to actual requirements, or the terminal device may also randomly select one MCS configuration from the determined MCS configurations, or the terminal device may also select one MCS configuration from the determined MCS configurations under a preset rule. Exemplarily, the preset rule may be to select one MCS configuration in the order of the reception time of the MCS configuration information. Or, the preset rule is to select according to the spectral efficiency of the MCS configuration information. Or, the preset rule is to select according to the coding rate of the MCS configuration information. Or, the preset rule is to select according to the spectral efficiency and coding rate of the MCS configuration information, and so on.

[0151] 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 may select one MCS configuration from the 3 MCS configurations.

[0152] The above 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 methods for 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 embodiments is used. In the RRC connected state, the base station configures MCS table indication information to indicate which MCS table to use, configures MCS configuration information to indicate an MCS in the MCS table, and configures tp-pi2BPSK to indicate the value of parameter q. In the RRC connected state, the network device can schedule UEs with the same UE capabilities within the same BWP. For example, the network device can only schedule UEs that support qam64LowSE within the first BWP. Then, within the first BWP, the network device can use the MCS table indication information to indicate which MCS table to use. Another example is that the network device can only schedule UEs that support pi / 2BPSK within the first BWP. Then, within the first BWP, the network device can use tp-pi2BPSK to indicate the value of parameter q. Another example is that in the non-RRC connected state, the MCS table of qam64 or qam64LowSE is used by default, and in the RRC connected state, the MCS configuration method in the above embodiments is used.

[0153] Embodiment 2:

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

[0155] S501. The terminal device receives two PUSCH configurations. Among them, the first PUSCH configuration corresponds to a first communication state, and the second PUSCH configuration corresponds to a second communication state. The two PUSCH configurations are used to configure the PUSCH resources in the two-step random access process.

[0156] Exemplarily, the first communication state may be the RRC connected state, and the second communication state is the non-RRC connected state, such as the RRC idle state or the RRC inactive state. Or, the second communication state may be the RRC connected state, and the first communication state is the non-RRC connected state, such as the RRC idle state or the RRC inactive state. Hereinafter, the case where the first communication state is the RRC connected state and the second communication state is the non-RRC connected state will be used as an example for description.

[0157] Among them, for the same type of parameters in the first PUSCH configuration and the second PUSCH configuration, the field length of this parameter in the first PUSCH configuration may be different from that in the second PUSCH resource. The content indicated by this parameter in the first PUSCH configuration may also be different from that indicated in the second PUSCH resource.

[0158] 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 instance, the MCS configuration information in the first PUSCH configuration is 5 bits, and the value range is 0 to 31, while the MCS configuration information in the second PUSCH configuration is 4 bits, and the value range is 0 to 15.

[0159] The content indicated by the MCS configuration information in the first PUSCH configuration and the second PUSCH configuration may be the same or different. It can also be understood that for the first PUSCH configuration and the second PUSCH configuration, the interpretation of the MCS configuration information may be the same or different. For example, the MCS configuration information i in the first PUSCH configuration may indicate the MCS with the MCS index i in the MCS table, and the MCS configuration information i in the second PUSCH configuration may indicate the MCS with the MCS index 2*i in the MCS table.

[0160] It can be understood that the value ranges and / or the content indicated by other configuration information in the first PUSCH configuration and the second PUSCH configuration may also be different.

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

[0162] For another example, the frequency-domain resource size of msgA PUSCH in the second PUSCH configuration may be 2 bits, and the value range is {1, 2, 3, 6} RBs. The time-domain resource configuration information of msgA PUSCH in the first PUSCH configuration may also be 2 bits, and the value range is {2, 4, 6, 12} RBs. Or the time-domain resource configuration information of msgA PUSCH in the first PUSCH configuration may be 4 bits, and the value range is {1, 2, 3, 4, 5, 6, 8, 9, 10} RBs.

[0163] For another example, in the second PUSCH configuration, neither the subcarrier spacing of the preamble for two-step random access nor the target receiving power of the preamble needs to be configured, and the corresponding parameters of four-step random access are used. In the first PUSCH configuration, the resources for four-step random access may not be configured on some BWPs. If two-step random access resources are configured on these BWPs, the subcarrier spacing of the preamble and the target receiving power of the preamble need to be configured independently.

[0164] 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 both the first PUSCH configuration information and the second PUSCH configuration information do not include 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 element offset configuration information, PTRS power configuration information, sample density configuration information.

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

[0166] For example, in the licensed band, the guard interval of msgA PUSCH may 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 band, the guard interval of msgA PUSCH may be 2 bits, and the value range is {0, 2, 4, 6} OFDM symbols.

[0167] S502. The terminal device uses the corresponding PUSCH configuration according to the communication state it is in.

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

[0169] In the embodiments of the present application, in the RRC connected state and the non-RRC connected state, due to different service types and service sizes, different value ranges and / or indicated contents of the same resource configuration parameters can be used to more flexibly configure the resources in the RRC connected state and the non-RRC connected state.

[0170] It should be noted that the above two embodiments can be implemented as independent solutions respectively, or combined as a solution. The present application does not make specific limitations.

[0171] In the above embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspectives of the network device, the terminal device, and the interaction between the network device and the terminal device. To implement each function in the methods provided by the above embodiments of the present application, the network device and the terminal device may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. Whether a certain function among the above functions is executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module depends on the specific application and design constraint conditions of the technical solution.

[0172] As Figure 6 shown, based on the same inventive concept, the embodiments of the present application further provide an MCS configuration device 600. The device 600 can be a terminal device or a network device, or a device in the terminal device or the network device (for example, a chip or a chip system or a chipset or a part of the chip for executing the relevant method functions), or a device that can be used in matching with the terminal device or the network device. In one design, the device 600 can include modules corresponding one by one to the methods / operations / steps / actions executed by the terminal device or the network device in the above method embodiments. The module can be a hardware circuit, software, or a combination of a hardware circuit and software. In one design, the device can include a processing module 601 and a communication module 602.

[0173] In one implementation manner, the MCS configuration device can be specifically used to implement Figure 4A method executed by a terminal device in an embodiment. Among them, a communication module 602 is configured to receive MCS configuration information, and the MCS configuration information is used to indicate at least one of the following: a first MCS configuration and a second MCS configuration, where the first MCS configuration is an MCS configuration in a first MCS table, and the second MCS configuration is an MCS configuration in a second MCS table. A 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, and the MCS table is the first MCS table or the second MCS table.

[0174] In an exemplary illustration, the MCS configuration information is used to indicate the first MCS configuration. Specifically, the processing module 601 is configured to: if the first MCS table is not supported and the first MCS configuration belongs to the second MCS table, determine an MCS index in the second MCS table according to the MCS configuration information, and the MCS configuration indicated by the MCS index in the second MCS table is the same as the first MCS configuration; determine the MCS configuration indicated by the MCS index in the second MCS table according to the MCS index.

[0175] Exemplarily, when the MCS index of the first MCS configuration 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.

[0176] In another exemplary illustration, the MCS configuration information is used to indicate the first MCS configuration; specifically, the processing module 601 is configured to: if the first MCS table is not supported and the first MCS configuration does not belong to the second MCS table, do not use the MCS configuration indicated by the MCS configuration information.

[0177] Exemplarily, when the MCS index of the first MCS configuration 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.

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

[0179] In still another exemplary illustration, the MCS configuration information is used to indicate the first MCS configuration and the second MCS configuration. Specifically, the processing module 601 is configured to: 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, determine the second MCS configuration in the second MCS table according to the MCS configuration information.

[0180] Among them, the first MCS configuration and the second MCS configuration may be the same.

[0181] Exemplarily, the MCS configuration information can 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.

[0182] In another implementation manner, the MCS configuration device can specifically be used to implement Figure 4 the method executed by the network device in the embodiment of. Among them, the communication module 602 is used to send MCS configuration information, and the MCS configuration information is used to indicate at least one of the following: the first MCS configuration and the second MCS configuration, where the first MCS configuration is an MCS configuration in the first MCS table, and the second MCS configuration is an MCS configuration in the second MCS table.

[0183] In an exemplary description, the MCS configuration information is used to indicate the first MCS configuration.

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

[0185] In yet another exemplary description, the MCS configuration information is used to indicate the first MCS configuration and the second MCS configuration.

[0186] Among them, the first MCS configuration and the second MCS configuration can be the same.

[0187] Exemplarily, the MCS configuration information can 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.

[0188] In another implementation manner, the MCS configuration device can specifically be used to implement Figure 5 the method executed by the terminal device in the embodiment of. 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 PUSCH resources in the two-step random access process; the processing module 601 is used to use the corresponding PUSCH configuration according to the communication state it is in.

[0189] Exemplarily, the field lengths of the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource can be different.

[0190] The content indicated by the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource can also be different.

[0191] The processing module 601 can specifically be used to: use the first PUSCH configuration when in the first communication state; or use the second PUSCH configuration when in the second communication state.

[0192] In another implementation manner, the MCS configuration device may specifically be used to implement Figure 5 the method executed by the network device in the embodiment of

[0193] Exemplarily, the field lengths of the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource may be different.

[0194] The content indicated by the parameters in the first PUSCH configuration and the parameters in the second PUSCH resource may also be different.

[0195] The processing module 601 and the communication module 602 may also be used to execute the other corresponding steps or operations executed by the terminal device or the terminal device in the foregoing method embodiment, which will not be elaborated herein one by one.

[0196] The division of modules in the embodiments of the present application is illustrative, merely a logical function division. In actual implementation, there may be other division methods. In addition, in each embodiment of the present application, each functional module may be integrated in a processor, may also exist physically alone, or two or more modules may be integrated in one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0197] Such as Figure 7Device 700 provided by an embodiment of the present application is shown, which is used to implement the functions of the MCS configuration device 600 in the above method. This device can be a communication device, or a device in a communication device (for example, a chip or a chip system or a chipset or a part of a chip used to execute relevant method functions), or a device that can be used in combination with a communication device. The communication device can be a terminal device or a network device. Among them, this device can be a chip system. In an embodiment of the present application, the chip system can be composed of chips, or can include chips and other discrete devices. Device 700 includes at least one processor 720, which is used to implement the functions of the terminal device or the network device in the method provided by the embodiment of the present application. Device 700 may also include a communication interface 710. In an embodiment of the present application, the communication interface 710 can be a transceiver, a circuit, a bus, a module or other types of communication interfaces, and is used to communicate with other devices through a transmission medium. For example, when implementing the functions of a terminal device, the communication interface 710 is used for the device in device 700 to communicate with other devices. Exemplarily, this other device can 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 above method embodiment. Exemplarily, the communication interface 710 is used to receive MCS configuration information, and the MCS configuration information is used to indicate at least one of the following: a first MCS configuration, a second MCS configuration, where the first MCS configuration is an MCS configuration in a first MCS table, and the second MCS configuration is an MCS configuration in a second MCS table; the processor 720 is used to determine the MCS configuration in the supported MCS table according to the MCS configuration information received by the communication module, and the MCS table is the first MCS table or the second MCS table. The processor 720 and the communication interface 710 can also be used to perform other corresponding steps or operations executed by the terminal device in the above method embodiment, which will not be elaborated here one by one.

[0198] Device 700 may also include at least one memory 730, which is used to store program instructions and / or data. The memory 730 is coupled to the processor 720. The coupling in an embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information interaction between devices, units or modules. The processor 720 may cooperate with the memory 730. The processor 720 may execute the program instructions stored in the memory 730. At least one of the at least one memories may be included in the processor.

[0199] In an embodiment of the present application, the specific connection medium between the above communication interface 710, processor 720 and memory 730 is not limited. In the embodiment of the present application Figure 7 it is connected by a bus 740 between the memory 730, the processor 720 and the communication interface 710, and the bus is inFigure 7 is represented by a thick line. The connection manners between other components are only for illustrative purposes and are not limiting. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of convenience of representation, Figure 7 is only represented by a thick line, but it does not mean that there is only one bus or one type of bus.

[0200] In one embodiment, when device 600 and device 700 are specifically chips or chip systems, the information output or received by communication module 601 and communication interface 710 can be in the form of baseband signals. For example, when device 600 and device 700 implement the functions of a terminal device, the baseband signals carrying MCS configuration information are received by communication module 602 and communication interface 710. The MCS configuration information mentioned in this application is sent by a network device, which only indicates that the source of the information "MCS configuration information" is the network device, and does not mean that this information must be directly obtained by device 600 and device 700 from the network device. That is, the original signal (such as a radio frequency signal) carrying "MCS configuration information" sent by the network device is delivered to the communication interfaces of device 600 and 700 after being processed by other components or parts in the devices where device 600 and 700 are located.

[0201] In one embodiment, when device 600 and device 700 are specifically devices, the information output or received by communication module 602 and communication interface 710 can be radio frequency signals. For example, when device 600 and device 700 implement the functions of a terminal device, the radio frequency signals carrying MCS configuration information are received by communication module 602 and communication interface 710.

[0202] In the embodiments of the present application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0203] In the embodiments 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 may also be a volatile memory, such as a random-access memory (RAM). The memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiments of the present application may also be a circuit or any other device capable of implementing a storage function, for storing program instructions and / or data.

[0204] Figure 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 Figure 1 the system shown in Figures 4 - 5 and perform the functions of the terminal device in the method embodiment described above. For the sake of convenience of description, Figure 8 only the main components of the terminal device are shown. As Figure 8 shown, the terminal device 80 includes a processor, a memory, a control circuit, an antenna, and an input / output device. The processor is mainly used for processing communication protocols and communication data, and controlling the entire terminal device, executing software programs, and processing data of software programs. For example, it is used to support the terminal device to execute the Figures 4 - 5 actions described in the method embodiment above. The memory is mainly used for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals. The control circuit and the antenna together can also be called a transceiver, mainly used for transceiving radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, a display screen, a keyboard, etc., is mainly used for receiving data input by the user and outputting data to the user.

[0205] After the terminal device is powered 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 wirelessly transmitted, the processor performs baseband processing on the data to be transmitted and then outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal outward 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. The processor converts the baseband signal into data and processes the data.

[0206] Those skilled in the art can understand that for the sake of convenience of description, Figure 8Only one memory and one processor are shown. In an actual terminal device, there may be multiple processors and multiple memories. The memory can also be referred to as a storage medium or a storage device, etc. The memory can be a storage element on the same chip as the processor, i.e., an on-chip storage element, or an independent storage element. The embodiments of the present application do not limit this.

[0207] As an alternative implementation, the terminal device may include a baseband processor and a central processor. The baseband processor is mainly used to process communication protocols and communication data, and the central processor is mainly used to control the entire terminal device, execute software programs, and process data of software programs. Figure 8 The processor in can integrate the functions of the baseband processor and the central processor. Those skilled in the art can understand that the baseband processor and the central processor can also be independent processors, interconnected through technologies such as a bus. Those skilled in the art can understand that the terminal device can include multiple baseband processors to adapt to different network systems, and the terminal device can include multiple central processors to enhance its processing ability. Each component of the terminal device can be connected through various buses. The baseband processor can also be referred to as a baseband processing circuit or a baseband processing chip. The central processor can also be referred to as a central processing circuit or a central processing chip. The function of processing communication protocols and communication data can be built into the processor or stored in the memory in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0208] In the embodiments of the present application, the antenna and the control circuit with transceiver functions can be regarded as the transceiver unit 801 of the terminal device 80. For example, it is used to support the terminal device to execute receiving and sending functions. The processor 802 with processing functions is regarded as the processing unit 802 of the terminal device 80. As Figure 8 shown, the terminal device 80 includes a transceiver unit 801 and a processing unit 802. The transceiver unit can also be referred to as a transceiver, a transceiver machine, a transceiver device, etc. Optionally, the device in the transceiver unit 801 for implementing the receiving function can be regarded as the receiving unit, and the device in the transceiver unit 801 for implementing the sending function can be regarded as the sending unit, that is, the transceiver unit 801 includes a receiving unit and a sending unit. The receiving unit can also be referred to as a receiver, an input port, a receiving circuit, etc., and the sending unit can be referred to as a transmitter, a transmitter, or a transmitting circuit, etc.

[0209] The processor 802 can be used to execute the instructions stored in the memory to control the transceiver unit 801 to receive signals and / or send signals, and complete the functions of the terminal device in the above method embodiments. The processor 802 also includes an interface to implement the input / output function of signals. As an implementation, the function of the transceiver unit 801 can be considered to be implemented through a transceiver circuit or a dedicated chip for transceiver.

[0210] Figure 9 This is a schematic structural diagram of a network device provided by an embodiment of the present application. For example, it can be a schematic structural diagram of a base station. As Figure 9 shown, this network can be applied to, for example, Figure 1 the system shown in Figures 4 - 5 to perform the functions of the network device in the method embodiment described 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 is mainly used for the transceiver of radio frequency signals, the conversion between radio frequency signals and baseband signals, and partial baseband processing. The CU 902 may include at least one processor 9022 and at least one memory 9021. Communication can be carried out between the CU 902 and the DU 901 through an interface. Among them, the control plane (Controlplan) interface can be Fs-C, such as F1-C, and the user plane (User Plan) interface can be Fs-U, such as F1-U.

[0211] The CU 902 is mainly used for baseband processing, controlling the base station, etc. The DU 901 and the CU 902 may be physically set together or physically separated, that is, a distributed base station. The CU 902 is the control center of the base station and can also be called a processing unit, mainly used to complete the baseband processing function. For example, the CU 902 can be used to control the base station to execute the Figures 4 - 5 operation process of the network device in the method embodiment described above.

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

[0213] 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. Among them, 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.

[0214] In one example, the CU902 may be composed of one or more single boards. The multiple single boards may jointly support a radio access network with a single access indication (such as a 5G network), or may separately support radio access networks with different access systems (such as an LTE network, a 5G network, or other networks). The memory 9021 and the processor 9022 may serve one or more single boards. That is to say, a memory and a processor may be separately provided on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board. The DU901 may be composed of one or more single boards. The multiple single boards may jointly support a radio access network with a single access indication (such as a 5G network), or may separately support radio access networks with different access systems (such as an LTE network, a 5G network, or other networks). The memory 9014 and the processor 909 may serve one or more single boards. That is to say, a memory and a processor may be separately provided on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board.

[0215] An 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 is enabled to implement the above MCS configuration method.

[0216] An embodiment of the present application also provides a computer program product. When the computer program product is executed by a communication device, the communication device is enabled to implement the above MCS configuration method.

[0217] Those skilled in the art should understand that the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application may take 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 code.

[0218] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, 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 devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for implementing in the process Figure 1 one process or multiple processes and / or blocks Figure 1means for the functions specified in one or more blocks.

[0219] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including an instruction means that implements the functions specified in one Figure 1 or more processes and / or blocks Figure 1 means for the functions specified in one or more blocks.

[0220] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus, such that a series of operational steps are performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions specified in one Figure 1 or more processes and / or blocks Figure 1 means for the functions specified in one or more blocks.

[0221] Although the preferred embodiments of the present application have been described, additional changes and modifications can be made by those skilled in the art once they learn of the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications falling within the scope of the present application.

[0222] 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. Thus, 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 changes and modifications.

Claims

1. A method for configuring a Modulation and Coding Scheme (MCS), characterized in that, Including: The terminal device receives MCS configuration information, where the MCS configuration information is used to indicate the first MCS configuration in the first MCS table, or the MCS configuration information is used to indicate the first MCS configuration in the first MCS table and the second MCS configuration in the second MCS table. Here, the highest modulation order supported by the first MCS table and the second MCS table is the same; the spectral efficiency of the first MCS table is lower than the spectral efficiency supported by the second MCS table, and / or the code rate supported by the first MCS table is lower than the code rate supported by the second MCS table. The terminal device determines the MCS configuration in the first MCS table or the second MCS table according to the MCS configuration information.

2. The method according to claim 1, wherein The MCS configuration information is used to indicate the first MCS configuration. The terminal device determines the MCS configuration in the first MCS table or the second MCS table according to the MCS configuration information, including: If the terminal device does not support the first MCS table and the first MCS 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, and the MCS configuration indicated by the MCS index in the second MCS table is the same as the first MCS 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 When the MCS index of the first MCS configuration 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 first MCS configuration. The terminal device determines the MCS configuration in the first MCS table or the second MCS table according to the MCS configuration information, including: If the terminal device does not support the first MCS table and the first MCS 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, characterized in that, When the MCS index of the first MCS configuration 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.

6. The method according to claim 2 or 4, characterized in that, The range indicated by the MCS configuration information is a subset of the MCS configurations in the first MCS table.

7. The method according to claim 1, wherein The MCS configuration information is used to indicate the first MCS configuration and the second MCS configuration. The terminal device determines the MCS configuration in the first MCS table or the second MCS table according to the MCS configuration information, including: 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 according to claim 7, wherein The first MCS configuration is the same as the second MCS configuration.

9. The method according to claim 1, characterized in that, The MCS configuration information is further 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.

10. A modulation and coding scheme (MCS) configuration device, characterized in that It includes: A communication module, configured to receive MCS configuration information, where the MCS configuration information is used to indicate a first MCS configuration in a first MCS table, or the MCS configuration information is used to indicate the first MCS configuration in the first MCS table and a second MCS configuration in a second MCS table, where the highest modulation order supported by the first MCS table and the second MCS table is the same; the spectral efficiency of the first MCS table is lower than the spectral efficiency supported by the second MCS table, and / or the code rate supported by the first MCS table is lower than the code rate supported by the second MCS table; A processing module, configured to: determine an MCS configuration in the first MCS table or the second MCS table according to the MCS configuration information received by the communication module.

11. The device according to claim 10, characterized in that, The MCS configuration information is used to indicate the first MCS configuration; The processing module is specifically configured to: If the first MCS table is not supported and the first MCS configuration belongs to the second MCS table, determine an MCS index in the second MCS table according to the MCS configuration information, where the MCS configuration indicated by the MCS index in the second MCS table is the same as the first MCS configuration; Determine the MCS configuration indicated by the MCS index in the second MCS table according to the MCS index.

12. The device according to claim 11, wherein When the MCS index of the first MCS configuration 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.

13. The device according to claim 10, characterized in that, The MCS configuration information is used to indicate the first MCS configuration; The processing module is specifically configured to: If the first MCS table is not supported and the first MCS configuration does not belong to the second MCS table, do not use the MCS configuration indicated by the MCS configuration information.

14. The device according to claim 13, characterized in that When the MCS index of the first MCS configuration 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.

15. The device according to claim 11 or 13, characterized in that The range indicated by the MCS configuration information is a subset of the MCS configurations in the first MCS table.

16. The device according to claim 10, characterized in that, The MCS configuration information is used to indicate the first MCS configuration and the second MCS configuration; The processing module is specifically configured to: 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, determine the second MCS configuration in the second MCS table according to the MCS configuration information.

17. The device according to claim 16, characterized in that, The first MCS configuration is the same as the second MCS configuration.

18. The device according to claim 10, characterized in that, The MCS configuration information is further 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.

19. A computer-readable storage medium, characterized in that, A program or instruction is stored in the computer-readable storage medium, and when the program or the instruction is read and executed by one or more processors, the method according to any one of claims 1 to 9 can be implemented.

20. 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 9.

Citation Information

Patent Citations

  • Method for transmitting signaling and receiving MCS

    CN104065446A

  • MCS index table configuration method, user terminal and network side device

    CN109787711A