CN117676841A

CN117676841A - Downlink Control Information (DCI) transmission method and device, terminal and network equipment

Info

Publication number: CN117676841A
Application number: CN202210969037.XA
Authority: CN
Inventors: 李娜; 曾超君
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-08-12
Filing date: 2022-08-12
Publication date: 2024-03-08

Abstract

The application discloses a Downlink Control Information (DCI) transmission method and device, a terminal and network side equipment, which belong to the technical field of communication, and the DCI transmission method comprises the following steps: the network side equipment sends DCI to the terminal, wherein the DCI comprises at least one of the following components: a frequency domain resource allocation, FDRA, domain for indicating allocated frequency domain resources of the scheduled at least one physical shared channel; a modulation and coding scheme, MCS, field for indicating an MCS index of the scheduled at least one physical shared channel; wherein the physical shared channel comprises a physical uplink shared channel or a physical downlink shared channel. The embodiment of the application can improve the flexibility of frequency domain resource allocation.

Description

Downlink Control Information (DCI) transmission method and device, terminal and network equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a Downlink Control Information (DCI) transmission method and device, a terminal and network side equipment.

Background

Multi-PXSCH (physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) or physical downlink shared channel (Physical Downlink Shared Channel, PDSCH)) scheduling may save physical downlink control channel (Physical Downlink Control Channel, PDCCH) overhead, which may be beneficial to improve system throughput. However, in the prior art, the frequency domain allocation resources, modulation and coding strategies (Modulation and Coding Scheme, MCS) and the like of multiple PDSCH scheduled by one downlink control information (Downlink Control Information, DCI) are the same, and cannot adapt to different resource allocation or channel variation, so that the scheduling flexibility of the base station is limited.

Disclosure of Invention

The embodiment of the application provides a Downlink Control Information (DCI) transmission method and device, a terminal and network side equipment, which can improve the flexibility of frequency domain resource allocation.

In a first aspect, a downlink control information DCI transmission method is provided, including:

the network side equipment sends DCI to the terminal, wherein the DCI comprises at least one of the following components:

a frequency domain resource allocation, FDRA, domain for indicating allocated frequency domain resources of the scheduled at least one physical shared channel;

a modulation and coding scheme, MCS, field for indicating an MCS index of the scheduled at least one physical shared channel;

wherein the physical shared channel comprises a physical uplink shared channel or a physical downlink shared channel.

In a second aspect, a downlink control information DCI transmission device is provided, including:

a sending module, configured to send DCI to a terminal, where the DCI includes at least one of:

In a third aspect, a method for transmitting downlink control information DCI is provided, including:

the terminal receives DCI of network side equipment, wherein the DCI comprises at least one of the following components:

the terminal determines the allocated frequency domain resource and/or MCS index according to the DCI;

In a fourth aspect, a downlink control information DCI transmission device is provided, including:

a receiving module, configured to receive DCI of a network side device, where the DCI includes at least one of:

determining allocated frequency domain resources and/or MCS indexes according to the DCI;

In a fifth aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which program or instructions when executed by the processor implement the steps of the method as described in the first aspect.

In a sixth aspect, a network side device is provided, including a processor and a communication interface, where the communication interface is configured to send DCI to a terminal, and the DCI includes at least one of:

In a seventh aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method according to the third aspect.

An eighth aspect provides a terminal, including a processor and a communication interface, where the communication interface is configured to receive DCI of a network side device, the DCI includes at least one of:

the processor is used for determining allocated frequency domain resources and/or MCS indexes according to the DCI;

In a ninth aspect, there is provided a communication system comprising: the network side device may be configured to perform the steps of the downlink control information DCI transmission method according to the first aspect, and the terminal may be configured to perform the steps of the downlink control information DCI transmission method according to the third aspect.

In a tenth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect, or performs the steps of the method according to the third aspect.

In an eleventh aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being for running a program or instructions to implement the method according to the first aspect or to implement the method according to the third aspect.

In a twelfth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executed by at least one processor to implement the downlink control information, DCI, transmission method according to the first aspect or to implement the steps of the downlink control information, DCI, transmission method according to the third aspect.

In the embodiment of the application, the DCI comprises an FDRA domain and an MCS domain, wherein the FDRA domain can indicate the allocated frequency domain resources of one or more physical shared channels to be scheduled, so that the flexibility of the frequency domain resource allocation during the multi-physical shared channel scheduling can be improved, and the size of the DCI can be effectively reduced; the MCS field can indicate MCS indexes of one or more physical shared channels to be scheduled, and can improve flexibility of MCS indication and effectively reduce DCI size.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a flow chart of a DCI transmission method at a network device side according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a terminal-side DCI transmission method according to an embodiment of the present application;

fig. 4 is a block diagram of a network-side DCI transmission device according to an embodiment of the present application;

Fig. 5 is a block diagram of a terminal-side DCI transmission device according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a network side device according to an embodiment of the present application.

Detailed Description

Technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application are within the scope of the protection of the present application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the terms "first" and "second" are generally intended to be used in a generic sense and not to limit the number of objects, for example, the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It is noted that the techniques described in embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the present application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and NR terminology is used in much of the description below, but these techniques may also be applied to applications other than NR system applications, such as the 6th generation (6th Generation,6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. Note that, the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiments of the present application, only a base station in an NR system is described as an example, and the specific type of the base station is not limited.

In NR, the concept of Multiple PUSCH/PDSCH scheduling is introduced, and a single DCI (e.g., DCI Format 0_1/1_1) may schedule 1 to Multiple resources that are consecutive in time for transmitting PUSCH/PDSCH, so as to save the overhead of the base station issuing DCI. Specifically, one DCI may schedule multiple PDSCH/PUSCH transmissions, each of which may transmit a different Transport Block (TB).

Hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ) process (process) Identification (ID): the HARQ process number field in the DCI indicates the HARQ process ID of the first PDSCH/PUSCH transmission scheduled, the remainder being sequentially incremented by 1 according to transmission timing (occalation).

Frequency domain resource allocation (Frequency domain resource assignment, FDRA): indicated by the Frequency domain resource assignment field in DCI, the frequency domain resources allocated for all PDSCH/PUSCH scheduled for one DCI are the same.

Frequency hopping (Frequency hopping) is indicated by the Frequency hopping flag field in DCI, all PDSCH/PUSCH scheduled for one DCI are the same.

Time domain resource allocation (time domain resource assignment, TDRA): the base station configures a TDRA table, each row in the table may contain a number of slot offsets K0 and start and length indicators SLIV (for PDSCH) and mapping type (for PUSCH) or (K2 SLIV, mapping type) combinations, i.e. the time domain resource allocation indicating different PXSCHs may be different.

Modulation and coding scheme (Modulation and coding scheme, MCS) indicated by the Modulation and coding scheme field in DCI, all PDSCH/PUSCH scheduled for one DCI are the same.

New data identification (New data indicator, NDI): indicated by the New data indicator field in the DCI, the number of bits in this field depends on the maximum number of PXSCHs scheduled for all entries in the TDRA table, one PXSCH per bit, i.e. each PXSCH indicates the corresponding NDI, respectively.

Redundancy versions (Redundancy version, RV) are indicated by the Redundancy version field in the DCI, the number of bits of which depends on the maximum number of PXSCHs scheduled by all entries in the TDRA table, one PXSCH per bit (note for single PXSCH schedule, 2 bits for RV for each PXSCH), i.e. each PXSCH indicates a corresponding RV, respectively.

NR uplink/downlink scheduling frequency domain resource allocation

The uplink/downlink scheduling frequency domain Resource allocation of NR is mainly used to determine a set of Resource Blocks (RBs) allocated for PUSCH/PDSCH transmission, and is indicated by the "Frequency domain Resource assignment" field in DCI Format 0_0/0_1/0_2 for uplink active scheduling. For downlink dynamic scheduling, indicated by the "Frequency domain resource assignment" field in DCI Format 1_0/1_1/1_2.

Rel-15 NR supports two uplink/downlink resource allocation schemes:

type 0

The resource blocks within the target upstream Bandwidth Part (BWP) of the resource allocation are divided into a plurality of resource block groups (Resource Block Group, RBG), each RBG corresponding to a set of up to P consecutive Virtual resource blocks (Virtual RB, VRB), P being determined by the following table 1 based on a higher layer parameter Configuration (indicating which column in table 1, configuration 1 or Configuration 2 is used), the number of resource blocks contained within the target upstream BWP.

Watch 1:P

Bandwidth Part Size	Configuration 1	Configuration 2
			1–36	2	4
37–72	4	8
			73–144	8	16
145–275	16	16

The "Frequency domain resource assignment" field in the DCI indicates whether each RBG in the target upstream BWP is allocated to the UE, using a Bitmap approach. Each bit in the Bitmap corresponds to each RBG in the target uplink BWP one-to-one, and when a certain bit in the Bitmap is set to 1, the corresponding RBG is indicated to be allocated to the UE, i.e. all resource blocks included in the RBG are allocated to the UE.

DCI Format 0_0/1_0 does not support uplink/downlink resource allocation type 0.

Type 1

Type 1 only supports a set of consecutively allocated non-interleaved VRBs, assuming that the starting VRB in this set is numbered RB _start (local numbering in target upstream BWP), the number of VRBs consecutively allocated is L _RBs The resource indicator value (Resource Indication ValueRIV) is calculated based on the following formula:

otherwise

Above-mentionedFor the number of VRB contained in the target uplink BWP, L _RBs Not less than 1 and not more than +.>

The RIV is indicated in the "Frequency domain resource assignment" field of the DCI, indicating the assigned set of VRBs to the UE.

Resource allocation type 1 supports frequency hopping (Frequency Hopping) transmissions, which may be indicated by the "Frequency hopping flag" field in DCI formats.

Determination of NR uplink scheduling modulation order and target code rate

Modulation and coding scheme applied to PUSCH/PDSCH transmission is indicated by DCI formats such as "Modulation and coding scheme" fields of 0_0/0_1, 1_0/1_1, "Modulation and coding scheme" field consisting of 5 bits, indicating values of I ranging from 0 to 31 _MCS . Based on I _MCS An application table corresponding to the following certain case is used for determining a Modulation Order (Modulation Order) Qm and a Target Code Rate (Target Code Rate) R of the PUSCH/PDSCH transmission application:

when Transform Precoding is not enabled, different tables are respectively corresponding in the following cases,

when 256QAM is supported;

when only 64QAM is supported and low spectral efficiency is used;

when only 64QAM is supported and conventional spectral efficiency is used;

When Transform Precoding is enabled, different tables are respectively corresponding in the following cases,

when 256QAM is supported;

when only 64QAM is supported and low spectral efficiency is used;

when only 64QAM is supported and conventional spectral efficiency is used.

Determination of NR uplink scheduling TB Size

When determining the bit number of a Transport Block (TB) corresponding to a PUSCH of a certain TB, two cases are distinguished:

case one: i _MCS Corresponding to the conventional MCS level, a target code rate R is indicated

For dynamic scheduling, I _MCS The value is taken for the 'Modulation and coding scheme' domain of DCI Format 0_0/0_1.

The UE first determines the effective RE number (N) of PUSCH-bearing TBs based on the following procedure _RE )：

First determining the physical resource block of the single physical resource blockPhysical Resource Block, PRB) allocates the number of REs (N 'for PUSCH transmission' _RE )，

Indicating the number of subcarriers within a single PRB;

the number of symbols occupied by the PUSCH;

the number of REs for DM-RS transmission within each PRB;

for the overhead configured by the higher layer parameters, if the higher layer is not configured, it is assumed +.>

Redetermining (N) _RE ) Is a value of (2);

N _RE ＝min(156,N' _RE )·n _PRB ；

n _PRB the number of PRBs occupied by the PUSCH;

then, the UE is based on the above (N _RE ) Target code rate R and modulation order Qm, number of layers of TB mapping determined by IMCS (for dynamic scheduling, "Modulation and coding scheme" field value of DCI Format 0_0/0_1) _υ The bit number of the TB is determined through operations such as quantization, table look-up and the like.

And a second case: IMCS (IMCS) corresponds to reserved MCS (modulation and coding scheme) level, and does not indicate target code rate R

At this time, the target code rate R is not explicitly indicated, and only the modulation order Qm is indicated to guide the modulation operation.

The UE assumes that the TB Size is equal to the TB Size indicated by the last DCI scheduling the same TB and using the normal MCS level.

XR service

Augmented reality (XR) refers to all real and virtual combined environments and human-machine interactions generated by computer technology and wearable devices. It includes representative forms of Augmented Reality (AR), mixed Reality (MR), virtual Reality (VR), etc., and the cross-domain between them. The level of the virtual world is from a partially sensory input to a fully immersive virtual reality. One key aspect of XR is the expansion of human experience, especially experience related to sense of presence (represented by VR) and cognition learning (represented by AR).

For VR business, the uplink is mainly transmitted by denser small data packets, and the small data packets can bear information such as gestures and control and serve as input and reference of downlink presentation data; the downlink mainly transmits multimedia data such as video and audio, and provides immersive feeling for users through timely receiving and presenting the multimedia data. Taking downstream video data as an example, the data packet arrives periodically or quasi-periodically, the data rate can reach several tens or even hundreds of Mbps, the typical value of FPS (frame rate) is 60 or 120, the interval between adjacent data packets is approximately 1/FPS seconds, these data generally need to be successfully transmitted within 10ms on the air interface, and the transmission success rate is required to be not lower than 99% or even 99.9%.

For AR service, uplink may transmit multimedia data such as video and audio in addition to the above dense small data packet transmission, and its service characteristics are similar to those of downlink, and the data rate is usually relatively low, for example, at most several tens Mbps, and the time limit of air interface transmission may be widened, for example, power transmission is generally required in 60ms, and in addition, for XR UL video service, the packet size may be changed for different frames; the downlink data transmission characteristics are substantially consistent with VR traffic.

In the prior art, multi-PXSCH scheduling, one DCI can schedule a plurality of PXSCs at a time. For XR service, the data packet is usually larger, and several PDSCH are usually required to complete transmission, and at this time, multi-PXSCH scheduling is used, so that DCI coverage can be effectively reduced, and system throughput is increased. However, in the prior art, all PXSCHs scheduled by one DCI can only indicate the same FDRA and MCS, and the best frequency domain resource cannot be selected for each PXSCH based on the channel state and/or the available resource condition, and the best matching MCS is selected for the frequency domain resource, the channel state, the initial/retransmission, and the like, so that the flexibility of resource allocation and the transmission performance are improved.

The downlink control information DCI transmission method provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings through some embodiments and application scenarios thereof.

An embodiment of the present application provides a downlink control information DCI transmission method, as shown in fig. 2, including:

step 101: the network side equipment sends DCI to the terminal, wherein the DCI comprises at least one of the following components:

In some embodiments, when the DCI schedules one or more physical shared channels (PXSCHs), the granularity of frequency domain resource allocation corresponding to each of the two physical shared channels (PXSCHs) is adopted, and by using different granularity of frequency domain resource allocation, the flexibility of frequency domain resource allocation during multi-PXSCH scheduling can be improved and the DCI size can be effectively reduced.

The number of bits in the FDRA domain may be n×m1, or a maximum value of n×m1 and N ', where N, M and N ' are positive integers, N and N ' are related to the bandwidth of the active bandwidth portion BWP and the resource allocation type, and M1 is related to the maximum number of physical shared channels that can be scheduled at one time or the number of physical shared channel groups, for example, the maximum number of PXSCHs that can be scheduled in all rows of the TDRA table corresponding to PXSCHs. The number of the physical shared channel groups is configured or preconfigured for the network side equipment or determined according to a predefined rule (for example, the maximum number of the PXSCs contained in each group is predefined or configured by the base station, and the number of the groups is determined according to the maximum number of the PXSCs which can be scheduled in all rows of the TDRA table corresponding to the PXSCs and the maximum number of the PXSCs contained in each group) or predefined by a protocol.

In some embodiments, N is related to granularity of the frequency domain resource allocation. Preferably, N is related to granularity of frequency domain resource allocation corresponding to when the DCI schedules a plurality of physical shared channels.

In some embodiments, in case the DCI schedules a plurality of physical shared channels, the FDRA domain is divided into M1 groups of bits, each group of bits including N bits, each group of bits to indicate allocated frequency domain resources of the scheduled one or a group of physical shared channels.

In some embodiments, in case that the DCI schedules one physical shared channel, N ' bits (e.g., N ' bits of the most significant MSB or the least significant LSB) of the FDRA domain are used to indicate allocated frequency domain resources of the one physical shared channel being scheduled, or the FDRA domain includes N ' bits. If N' is less than n×m1, zero padding may be required at the end of the DCI so that the DCI size is the same when scheduling a single PXSCH and multiple PXSCHs.

In some embodiments, N' is related to granularity of the frequency domain resource allocation. Preferably, N' is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules the one physical shared channel.

In the prior art, a base station configures a TDRA table of a PXSCH, where each row in the table may include one or more (K2, SLIV, mapping type) (for uplink) or (K0, SLIV, mapping type) (for downlink) combinations, and each (K2, SLIV, mapping type) (for uplink) or (K0, SLIV, mapping type) (for downlink) combination corresponds to one PXSCH.

One DCI format, e.g., DCI 0_1/1_1, may schedule both a single PXSCH and multiple PXSCHs. The scheduling of a single PXSCH or multiple PXSCHs may be judged by a row index indicated by a TDRA in DCI, which schedules a single pxssch if a row of a row index correspondence table indicated by a TDRA field in DCI contains only one (K2, SLIV, mapping type) (for uplink) or (K0, SLIV, mapping type) (for downlink) combination. If a row of the row index correspondence table indicated by the TDRA field in the DCI contains a plurality of (K2, SLIV, mapping type) (for the uplink) or (K0, SLIV, mapping type) (for the downlink) combinations, the DCI schedules a plurality of PXSCHs. When DCI 0_1 schedules PUSCH, the maximum number of PXSCHs that can be scheduled in all rows of the corresponding configuration TDRA table is nmax=8.

Since the size (size) of one DCI is determined, the DCI size is the same regardless of whether a single PXSCH or multiple PXSCHs are scheduled, so if multiple PXSCHs are scheduled, the FDRA indicating each group of PXSCH resource allocations contains the same number of bits as the FDRA when a single PXSCH is scheduled, which results in a larger DCI size and more redundancy bits when a single PXSCH is scheduled. Therefore, in this embodiment, the network side device may configure two or predefine granularity of two frequency domain allocations, when the DCI schedules a single PXSCH, a smaller granularity of frequency domain resource allocation is adopted, and when the DCI schedules a plurality of PXSCHs, a larger granularity of frequency domain resource allocation is adopted.

When multiple PXSCHs are scheduled, the FDRA field in the DCI may include FDRA1, FDRA2, …, and FDRAn to indicate the frequency domain resource allocation of each PXSCH in the plurality of PXSCHs that are scheduled, where one FDRAi (i=1, 2, … n) to PXSCH mapping may be one-to-one (i.e., each PXSCH has a corresponding single FDRA indicating its frequency domain resource allocation, e.g., m1=pxsch corresponds to the maximum number of PXSCHs that can be scheduled in all rows of the TDRA table), or many-to-one (i.e., a single FDRAi may indicate the frequency domain resource allocation of multiple PXSCHs, e.g., m1= (the maximum number of pxschsch that can be scheduled in all rows of the TDRA table that corresponds to pxschs—1)/2, where the mapping between FDRAi and PXSCH may be indicated by the base station or determined in a predefined manner), or a predefined M1 value, e.g., 2.

Thus, the bit number N of the FDRAi is smaller than the bit number N' of the FDRA in single PXSCH scheduling, and the total of the FDRAi can be similar to the bit number of the FDRA in single PXSCH scheduling as much as possible. For example, two frequency domain resource allocation granularities, i.e., a type 0 resource allocation, are set of resource blocks (Resource Block Group, RBG) size, with a single PXSCH scheduling corresponding to RBG size 1 and multiple PXSCH scheduling corresponding to RBG size 2. For type 1 Resource allocation, which is a Resource Block (RB), one RB corresponds to a single PXSCH schedule, a plurality of consecutive RBs correspond to a plurality of PXSCH schedules, and according to whether the single PXSCH or the plurality of PXSCHs are scheduled by the DCI, the UE and/or the network side device determines the granularity of frequency domain Resource allocation corresponding to the PXSCH scheduled by the DCI, and further determines the frequency domain Resource allocation corresponding to the PXSCH.

Specifically, for type 0, each RBG corresponds to a set of up to P consecutive Virtual Resource Blocks (VRBs), P being determined based on the higher-layer parameter Configuration (indicating which column in table 2 is used, whether Configuration 1 or Configuration 2), the number of resource blocks contained within the target upstream bandwidth portion (BWP), and table 2. The network side device may configure a single PXSCH schedule as configuration 1, and multiple PXSCH schedules as configuration 2. As such, the number of bits of the FDRAi may be less than half the number of bits required to schedule the FDRA for a single PXSCH (e.g., when BWP part size is not greater than 144).

Watch 2:Nominal RBG size P

For type 1 resource allocation, granularity of allocation is 1 VRB in the prior art, and FDRA domain indicates that RIV value corresponds to one initial VRBRB _start And a continuously allocated RB number length L _RBs Wherein RIV is defined as:

if it isThen

Otherwise

Wherein L is _RBs 1 and not exceed

When the DCI schedules a single PXSCH, the frequency domain resource allocation FDRA may be determined in the above manner, and when the DCI schedules multiple PXSCHs, the resource allocation may be performed with K VRBs as granularity, i.e. the starting VRBs corresponding to the RIV value indicated by FDRAi,and a continuously allocated RB number length L _RBs ，Thus, the bit number of FDRAi is smaller than that of single PXSCH scheduling, so that the DCI size can be reduced as much as possible, and the bit utilization rate in DCI can be improved.

For example, N and N' relate to bandwidth, resource allocation type, and in a specific example, for DCI 1_1, its FDRA bit number is determined as follows, whereIs the active downstream bandwidth size.

For the resource allocation type 0,wherein->The RBG size corresponding to the multi-PDSCH scheduling;the single PDSCH schedules the corresponding RBG size.

For the resource allocation type 1,wherein K represents granularity of multi-PDSCH scheduling time-frequency domain resource allocation, < >>

In some embodiments, the number of bits in the MCS field is x+y×m2 bits, where X, Y and M2 are positive integers, X and Y are predefined for the network side device configuration or protocol, for example, X is 5 bits and Y is 2 bits. M2 is related to the maximum number of physical shared channels which can be scheduled by the DCI at one time or the maximum number of physical shared channel groups which are configured or preconfigured for network side equipment or are determined or predefined according to a predefined rule or protocol, for example, the maximum number of PXSCs which can be scheduled in all rows of a TDRA table corresponding to the PXSCs.

In some embodiments, the X bits of the MCS field correspond to the first PXSCH of the schedule, and the remaining Y bits correspond to each of the remaining scheduled PXSCHs, i.e., in the case where the DCI schedules a plurality of physical shared channels, the plurality of physical shared channels are divided into 1+m2 groups of physical shared channels, each group of physical shared channels including one or more physical shared channels;

the X bits of the MCS field correspond to the first set of physical shared channels, the remaining Y X M2 bits are divided into M2 sets of bits, each set of bits including Y bits, and the M2 sets of bits correspond to the remaining M2 sets of physical shared channels one to one, for example, one scheduled PXSCH per Y bits, or one or more scheduled PXSCHs per Y bits.

In some embodiments, the X bits are used to indicate an MCS index (index) of the scheduled first set of physical shared channels. Each of the M2 sets of bits is used to indicate an offset of the MCS index of the corresponding physical shared channel set relative to the previous set of physical shared channels or the first set of physical shared channels.

For example, the MCS index of the scheduling PXSCH corresponding to Y is the MCS index+offset indicated by X, or the MCS index of the scheduling PXSCH corresponding to Y is determined as follows:

If the corresponding PXSCH is a new transmission, namely NDI is overturned, determining MCS index of the scheduling PXSCH corresponding to Y in the mode;

if the corresponding PXSCH is not new transmission, i.e. NDI is not flipped, determining MCS index corresponding to MCS index+offset indicated by X, determining modulation order corresponding to the index, and finding the MCS index identical to the modulation order in the stored MCS level in the MCS table;

in a specific example, for the MCS field of DCI 0_1, the modulation coding order MCS index for indicating the scheduled PXSCH, the number of bits of the field is determined according to the following manner:

x+y X M2 bits, where the number of bits of X, Y may be predefined or higher-level configured, e.g., X is 5 bits, Y is 2 bits, and M2 is related to the maximum number of PXSCHs or the number of PXSCH groups that can be scheduled at one time in multi-PXSCH scheduling, e.g., the maximum number N of PXSCHs that can be scheduled in all rows of the TDRA table corresponding to PXSCHs _max In relation, in particular, m2=floor ((N) _max -1)/2)。

The X bits correspond to the first or first group of PXSCHs scheduled, and each remaining Y bits correspond to the remaining scheduled pxss, e.g., the first Y bits correspond to the second or second group of scheduled PUSCHs, the second Y bits correspond to the third or third group and the last or last group of scheduled PUSCHs, it is noted that if the number of PUSCHs scheduled by a certain DCI is less than the maximum number, some bits may be left unused.

Wherein, X is used to indicate MCS index of the scheduled PXSCH, Y represents offset from MCS index of the previous or first scheduled PXSCH, and the offset may be positive integer or negative integer or 0, for example, when Y is 2 bits, the offset is-2,0,2,4, respectively.

Wherein, for the number of PXSCH groups and/or the PXSCH contained in each group, it may be a preconfigured or predefined rule determination, for example:

mode 1, maximum number N of PXSCH that can be scheduled by all rows in configured TDRA table _max Determining the number of groups of PXSCHs and/or the number of PXSCHs contained in each group

E.g. 3, N as preconfigured or predefined groups _max =8, then the first two groups, mod (N _max 3) PXSCH of floor (N) _max 3) =2, the last group contains PXSCH of N _max -8*floor(N _max /3)＝3。

Or predefining or configuring the number of PXSCs contained in each group of PXSCs to be 2 (representing at most not more than 2), and then according to N _max And the number of pxscs contained in each group of pxscs determines the number of pxscs groups, e.g., N _max =7, then the first 3 groups each contain 2 PXSCHs, the last group contains 1 PXSCH, or the first group contains 1 PXSCH, and the remaining 3 groups each contain 2 PXSCHs.

Mode 2: number N of PXSCs actually scheduled according to DCI _scheduled Determining the number of groups of pxscs and/or the number of pxscs contained in each group of pxscs

The actually scheduled PXSCH may be all PXSCHs included in the row corresponding to the TDRA indicated by the DCI, or may be the PXSCH that may be actually transmitted (e.g., if a certain SLIV indicated by the row corresponding to the TDRA overlaps with the semi-static UL/DL/SSB, the PXSCH corresponding to the SLIV cannot be transmitted, e.g., for the PUSCH, if a symbol indicated by a certain SLIV overlaps with the DL/SSB, the PUSCH corresponding to the SLIV cannot be transmitted), e.g., the number of PXSCHs included in each group of PXSCHs (i.e., the PXSCHs included in each group of PXSCHs are the same or different by 1):

let m=min (N _max ，N _scheduled )；

M1＝mod(N _scheduled ，M)；

K1＝cell(N _scheduled /M),K2＝floor(N _scheduled /M)；

If M1>0, for the first M groups of PXSCHs, i.e., m=0, 1,2, …, M1-1, each group of PXSCHs contains K1 consecutive pxs, i.e., each group of PXSCHs contains a pxs index of m×k1+k, k=0, 1, …, K1-1, and for m=m1, m1+1, …, M-1, each group of PXSCHs contains a pxs index of m1×k1+ (M-M1) ×k2+k, k=0, 1, … K2-1.

Or alternatively

If M1>0, for the first M groups of PXSCHs, i.e., m=0, 1,2, …, M-M1-1, each group of PXSCHs contains K2 consecutive pxs, i.e., each group of PXSCHs contains a pxs index of m×k2+k, k=0, 1, …, K2-1, and for m=m 1, M-m1+1, …, M-1, each group of pxs contains a PXSCH index of (M-M1) ×k2+ (M-m+m1) ×k1+k, k=0, 1, … K1-1.

The embodiment of the application also provides a DCI transmission method, as shown in fig. 3, including:

Step 201: the terminal receives DCI of network side equipment, wherein the DCI comprises at least one of the following components:

In some embodiments, when the DCI schedules one or more physical shared channels, granularity of respective corresponding frequency domain resource allocations is used.

In some embodiments, the number of bits in the FDRA domain is n×m1, or is the maximum value of n×m1 and N ', where N, M and N ' are positive integers, and N ' are both related to the bandwidth of the active bandwidth portion BWP and the resource allocation type, and M1 is related to the maximum number of physical shared channels or the number of physical shared channel groups that can be scheduled at one time by the DCI.

In some embodiments, N is related to granularity of the frequency domain resource allocation.

In some embodiments, N is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules a plurality of physical shared channels.

In some embodiments, in case that the DCI schedules one physical shared channel, N 'bits of the FDRA domain are used to indicate allocated frequency domain resources of the one physical shared channel being scheduled, or the FDRA domain includes N' bits.

In some embodiments, N' is related to granularity of the frequency domain resource allocation.

In some embodiments, N' is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules the one physical shared channel.

In some embodiments, the number of bits in the MCS field is x+y×m2 bits, where X, Y and M2 are positive integers, X and Y are predefined by a network side device configuration or a protocol, and M2 is related to the maximum number of physical shared channels or the number of physical shared channel groups that can be scheduled at a time by the DCI.

In some embodiments, in case the DCI schedules a plurality of physical shared channels, the plurality of physical shared channels are divided into 1+m2 groups of physical shared channels, each group of physical shared channels including one or more physical shared channels;

the X bits of the MCS domain correspond to the first group of physical shared channels, the remaining Y X M2 bits are divided into M2 groups of bits, each group of bits comprises Y bits, and the M2 groups of bits correspond to the remaining M2 groups of physical shared channels one by one.

In some embodiments, the X bits are used to indicate an MCS index for the scheduled first set of physical shared channels.

In some embodiments, each of the M2 sets of bits is used to indicate an offset of the MCS index of the corresponding physical shared channel set relative to the previous set of physical shared channels or the first set of physical shared channels.

In some embodiments, the number of physical shared channel groups is configured or preconfigured for the network side device or predefined according to a predefined rule or protocol.

In the DCI transmission method provided in the embodiment of the present application, the execution body may be a DCI transmission device. In the embodiment of the present application, a DCI transmission device executes a DCI transmission method as an example, and the DCI transmission device provided in the embodiment of the present application is described.

The embodiment of the present application provides a DCI transmission apparatus 300, which is applied to a network side device, as shown in fig. 4, including:

a transmitting module 310, configured to transmit DCI to a terminal, where the DCI includes at least one of:

The embodiment of the application also provides a DCI transmission device 400, which is applied to a terminal, as shown in fig. 5, and includes:

a receiving module 410, configured to receive DCI of a network side device, where the DCI includes at least one of:

The DCI transmission device in the embodiment of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The DCI transmission device provided in the embodiment of the present application can implement each process implemented in the method embodiments of fig. 2 to 3, and achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Optionally, as shown in fig. 6, the embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, where the memory 602 stores a program or an instruction that can be executed on the processor 601, for example, when the communication device 600 is a network side device, the program or the instruction implements each step of the DCI transmission method embodiment described above when executed by the processor 601, and the same technical effects can be achieved. When the communication device 600 is a terminal, the program or the instructions implement the steps of the DCI transmission method embodiment when executed by the processor 601, and achieve the same technical effects, so that repetition is avoided and no further description is given here.

The embodiment of the application also provides network side equipment, which comprises a processor and a memory, wherein the memory stores a program or instructions capable of running on the processor, and the program or instructions realize the steps of the DCI transmission method when being executed by the processor.

The embodiment of the application also provides network side equipment, which comprises a processor and a communication interface, wherein the communication interface is used for sending DCI to a terminal, and the DCI comprises at least one of the following:

The embodiment of the application also provides a terminal, which comprises a processor and a memory, wherein the memory stores a program or instructions executable on the processor, and the program or instructions realize the steps of the DCI transmission method when being executed by the processor.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is used for receiving DCI of network side equipment, and the DCI comprises at least one of the following:

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the terminal embodiment corresponds to the terminal side method embodiment, and each implementation process and implementation mode of the method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, fig. 7 is a schematic hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 700 includes, but is not limited to: at least some of the components of the radio frequency unit 701, the network module 702, the audio output unit 703, the input unit 704, the sensor 705, the display unit 706, the user input unit 707, the interface unit 708, the memory 709, and the processor 710.

Those skilled in the art will appreciate that the terminal 700 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 710 via a power management system so as to perform functions such as managing charging, discharging, and power consumption via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine certain components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 704 may include a graphics processing unit (Graphics Processing Unit, GPU) 7041 and a microphone 7042, with the graphics processor 7041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touch screen. The touch panel 7071 may include two parts, a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In this embodiment, after receiving downlink data from the network side device, the radio frequency unit 701 may transmit the downlink data to the processor 710 for processing; in addition, the radio frequency unit 701 may send uplink data to the network side device. Typically, the radio unit 701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 709 may be used to store software programs or instructions and various data. The memory 709 may mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 709 may include volatile memory or nonvolatile memory, or the memory 709 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 709 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

Processor 710 may include one or more processing units; optionally, processor 710 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 710.

In some embodiments, the processor 710 is configured to receive DCI of a network-side device, where the DCI includes at least one of:

The embodiment of the application also provides network side equipment which comprises a processor and a communication interface. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 8, the network side device 800 includes: an antenna 81, a radio frequency device 82, a baseband device 83, a processor 84 and a memory 85. The antenna 81 is connected to a radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information via the antenna 81, and transmits the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes information to be transmitted, and transmits the processed information to the radio frequency device 82, and the radio frequency device 82 processes the received information and transmits the processed information through the antenna 81.

The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 83, and the baseband apparatus 83 includes a baseband processor.

The baseband device 83 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 8, where one chip, for example, a baseband processor, is connected to the memory 85 through a bus interface, so as to call a program in the memory 85 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 86, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 800 of the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84, the processor 84 invokes the instructions or programs in the memory 85 to perform the DCI transmission method as described above and achieve the same technical effects, and are not repeated here.

The embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the processes of the embodiment of the DCI transmission method are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, implement each process of the DCI transmission method embodiment, and achieve the same technical effect, so that repetition is avoided, and no redundant description is given here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the embodiments of the DCI transmission method, and achieve the same technical effects, so that repetition is avoided and details are not repeated here.

The embodiment of the application also provides a communication system, which comprises: the network side device may be configured to perform the steps of the DCI transmission method described above, and the terminal may be configured to perform the steps of the DCI transmission method described above.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solutions of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. The Downlink Control Information (DCI) transmission method is characterized by comprising the following steps:

2. The method of claim 1, wherein the DCI schedules one or more physical shared channels with a granularity of frequency domain resource allocation corresponding to each.

3. The method of claim 1, wherein the number of bits in the FDRA domain is N x M1, or is a maximum of N x M1 and N ', wherein N, M and N ' are positive integers, N and N ' are each related to a bandwidth of an active bandwidth portion BWP and a resource allocation type, and M1 is related to a maximum number of physical shared channels or a physical shared channel group number that the DCI can schedule at one time.

4. A method according to claim 3, wherein N is related to the granularity of the frequency domain resource allocation.

5. The method of claim 4, wherein N is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules a plurality of physical shared channels.

6. The method of claim 3, wherein in the case where the DCI schedules a plurality of physical shared channels, the FDRA domain is divided into M1 groups of bits, each group of bits including N bits, each group of bits to indicate allocated frequency domain resources of a scheduled one or a set of physical shared channels.

7. The method of claim 1, wherein N 'bits of the FDRA domain are used to indicate allocated frequency domain resources of one physical shared channel scheduled in case that the DCI schedules the one physical shared channel, or the FDRA domain includes N' bits.

8. The method of claim 7, wherein N' is related to granularity of the frequency domain resource allocation.

9. The method of claim 8, wherein N' is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules the one physical shared channel.

10. The method of claim 1, wherein the number of bits of the MCS field is x+y X M2 bits, wherein X, Y and M2 are positive integers, X and Y are predefined by a network side device configuration or protocol, and M2 is related to a maximum number of physical shared channels or a number of physical shared channel groups that can be scheduled at one time by the DCI.

11. The method of claim 10, wherein in the case where the DCI schedules a plurality of physical shared channels, the plurality of physical shared channels are divided into 1+m2 groups of physical shared channels, each group of physical shared channels including one or more physical shared channels;

12. The method of claim 11, wherein the X bits are used to indicate an MCS index for the scheduled first set of physical shared channels.

13. The method of claim 12, wherein each of the M2 sets of bits is used to indicate an offset of the MCS index of the corresponding physical shared channel set relative to the previous set of physical shared channels or the first set of physical shared channels.

14. A method according to claim 3 or 10, characterized in that the number of physical shared channel groups is configured or preconfigured for network side devices or predefined according to predefined rules or protocols.

15. The Downlink Control Information (DCI) transmission method is characterized by comprising the following steps:

16. The method of claim 15, wherein the DCI schedules one or more physical shared channels using respective granularity of frequency domain resource allocation.

17. The method of claim 15, wherein the number of bits in the FDRA domain is N x M1, or is a maximum of N x M1 and N ', wherein N, M and N ' are positive integers, N and N ' are each related to a bandwidth of an active bandwidth portion BWP and a resource allocation type, and M1 is related to a maximum number of physical shared channels or a physical shared channel group number that the DCI can schedule at one time.

18. The method of claim 17, wherein N is related to granularity of the frequency domain resource allocation.

19. The method of claim 18, wherein N is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules a plurality of physical shared channels.

20. The method of claim 17, wherein in the case where the DCI schedules a plurality of physical shared channels, the FDRA domain is divided into M1 groups of bits, each group of bits including N bits, each group of bits to indicate allocated frequency domain resources of a scheduled one or a set of physical shared channels.

21. The method of claim 15, wherein N 'bits of the FDRA domain are used to indicate allocated frequency domain resources of one physical shared channel scheduled in case that the DCI schedules the one physical shared channel, or the FDRA domain includes N' bits.

22. The method of claim 21, wherein N' is related to granularity of the frequency domain resource allocation.

23. The method of claim 22, wherein N' is related to granularity of a corresponding frequency domain resource allocation when the DCI schedules the one physical shared channel.

24. The method of claim 15, wherein the number of bits of the MCS field is x+y X M2 bits, wherein X, Y and M2 are positive integers, X and Y are predefined by a network side device configuration or protocol, and M2 is related to a maximum number of physical shared channels or a number of physical shared channel groups that can be scheduled at one time by the DCI.

25. The method of claim 24, wherein, in the case where the DCI schedules a plurality of physical shared channels, the plurality of physical shared channels are divided into 1+m2 groups of physical shared channels, each group of physical shared channels including one or more physical shared channels;

26. The method of claim 25, wherein the X bits are used to indicate an MCS index for the scheduled first set of physical shared channels.

27. The method of claim 26, wherein each of the M2 sets of bits is used to indicate an offset of the MCS index of the corresponding set of physical shared channels relative to the previous set of physical shared channels or the first set of physical shared channels.

28. The method according to claim 17 or 24, wherein the number of physical shared channel groups is configured or preconfigured for network side devices or predefined according to predefined rules or protocols.

29. A downlink control information DCI transmission device, comprising:

30. A downlink control information DCI transmission device, comprising:

31. A terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the downlink control information, DCI, transmission method according to any one of claims 15 to 28.

32. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the downlink control information, DCI, transmission method according to any one of claims 1 to 14.

33. A readable storage medium, characterized in that a program or an instruction is stored on the readable storage medium, which when executed by a processor implements the downlink control information DCI transmission method according to any one of claims 1-14 or the steps of the downlink control information DCI transmission method according to any one of claims 15 to 28.