Multi-carrier scheduling method and apparatus

Abstract

Provided in the embodiments of the present application are a multi-carrier scheduling method and apparatus. The method comprises: a terminal device receiving downlink control information from a network device, wherein the downlink control information is used for scheduling the terminal device to perform uplink transmission over a plurality of cells, and the downlink control information is used for triggering aperiodic sounding reference signal transmission over the plurality of cells.

Description

Multi-carrier scheduling method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] In NR Rel-15 / 16 / 17, the Physical Uplink Shared Channel (PUSCH) transmits up to 4 layers and uses a single codeword (or a single transport block). The downlink control information (DCI) format for scheduling PUSCH, namely DCI format 0_1 / 0_2, includes the following fields: Modulation and Coding Scheme (MCS), New Data Indicator (NDI), and Redundancy Version (RV).

[0003] In NR Rel-18, multi-carrier scheduling has been enhanced. DCI format 0_3 has been introduced to schedule PUSCH transmissions on multiple component carriers (CCs) or multiple serving cells.

[0004] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0005] Summary of the Invention

[0006] The inventors found that DCI format 0_3 only includes one MCS / NDI / RV field, which means that it only supports single codeword operation, that is, DCI format 0_3 does not support up to 8 layers of PUSCH transmission. In order to support up to 8 layers of PUSCH, downlink control information should be enhanced.

[0007] To address at least one of the above problems, embodiments of the present application provide a multi-carrier scheduling method and apparatus.

[0008] According to one aspect of an embodiment of the present application, a multi-carrier scheduling method is provided, which is applied to a terminal device capable of supporting 8-transmission (8Tx) uplink transmission, the method comprising:

[0009] The terminal device receives downlink control information from the network device;

[0010] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

[0011] According to another aspect of an embodiment of the present application, a multi-carrier scheduling apparatus is provided, configured in a terminal device capable of supporting 8Tx uplink transmission, the apparatus comprising:

[0012] a receiving unit, configured to receive downlink control information from a network device;

[0013] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

[0014] According to another aspect of an embodiment of the present application, a multi-carrier scheduling method is provided, applied to a network device, the method comprising:

[0015] The network device sends downlink control information to the terminal device;

[0016] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

[0017] According to another aspect of an embodiment of the present application, a multi-carrier scheduling apparatus is provided, configured in a network device, the apparatus comprising:

[0018] A sending unit, which sends downlink control information to the terminal device;

[0019] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

[0020] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0021] A network device that sends downlink control information to a terminal device; the downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger aperiodic sounding reference signal transmission in the multiple cells;

[0022] A terminal device receives downlink control information from a network device.

[0023] One of the benefits of the embodiments of the present application is that downlink control information (e.g., DCI format 0_3) can schedule PUSCH transmissions with up to 8 layers. In addition, in DCI format 0_3, aperiodic SRS triggering can be decoupled from PUSCH scheduling, thereby increasing flexibility.

[0024] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0025] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0026] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0028] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0029] FIG2 is a schematic diagram of a multi-carrier scheduling method according to an embodiment of the present application;

[0030] FIG3 is a schematic diagram of a DCI format 0_3 supporting up to 8 layers of PUSCH transmission according to an embodiment of the present application;

[0031] FIG4 is another schematic diagram of the multi-carrier scheduling method according to an embodiment of the present application;

[0032] FIG5 is a schematic diagram of a multi-carrier scheduling apparatus according to an embodiment of the present application;

[0033] FIG6 is another schematic diagram of a multi-carrier scheduling apparatus according to an embodiment of the present application;

[0034] FIG7 is a schematic diagram of a network device according to an embodiment of the present application;

[0035] FIG8 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0036] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0037] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0038] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0039] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0040] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other communication protocols currently known or to be developed in the future.

[0041] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0042] Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB) and 5G base station (gNB), IAB host, etc., and may also include remote radio head (RRH, Remote Radio Head), remote radio unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0043] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0044] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0045] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0046] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0047] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0048] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0049] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0050] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0051] In NR Rel-15 / 16, aperiodic SRS transmission can be triggered by DCI format 0_1 / 0_2, and aperiodic SRS is triggered by the SRS request field in the DCI with a non-zero value. However, aperiodic SRS must be triggered together with the PUSCH, which limits aperiodic SRS transmission. Table 1 schematically shows the case where aperiodic SRS triggering is bundled with PUSCH.

[0052] Table 1

[0053] As shown in Table 1, in Rel-16, when aperiodic SRS is triggered in DCI format 0_1 / 0_2 (SRS request is non-zero), PUSCH must be triggered (UL-SCH indicator and CSI request cannot be set to zero at the same time), that is, aperiodic SRS triggering is bundled with PUSCH.

[0054] Rel-17 enhances aperiodic SRS triggering and decouples aperiodic SRS triggering from PUSCH, making it more flexible. Table 2 schematically shows the decoupling of aperiodic SRS triggering from PUSCH.

[0055] Table 2

[0056] As shown in Table 2, in Rel-17, if the UE only supports triggered SRS, the non-periodic SRS can be triggered by DCI format 0_1 / 0_2 without scheduling PUSCH (the UL-SCH indicator is set to 0 and the CSI request is set to zero), that is, the non-periodic SRS triggering is decoupled from PUSCH.

[0057] NR Rel-18 introduced 8Tx uplink transmission for PUSCH. A terminal device with 8Tx can support up to 8 layers of transmission in the uplink. To support up to 8 layers of transmission, dual codeword operation was introduced. Dual codewords are used for transmissions with a rank greater than 4.

[0058] In DCI format 0_1 ​​for scheduling PUSCH, two sets of MCS / NDI / RV fields are included. If the maximum rank (maxRank) is greater than 4, both sets of MCS / RV / NDI fields are included in DCI format 0_1; otherwise, the second set of MCS / NDI / RV fields does not exist.

[0059] In NR Rel-18, multi-carrier scheduling has been enhanced. DCI format 0_3 has been introduced to schedule PUSCH transmissions on multiple component carriers (CCs) or multiple serving cells.

[0060] However, DCI format 0_3 includes only one set of MCS / NDI / RV fields, which means that only single codeword operation is supported. That is, DCI format 0_3 does not support PUSCH transmission of up to 8 layers. To support up to 8 layers of PUSCH, DCI format 0_3 should be enhanced. Table 3 schematically illustrates the case where DCI format 0_3 only supports single codeword operation.

[0061] Table 3

[0062] In DCI format 0_3, aperiodic SRS triggering is still bundled with PUSCH. Table 4 schematically shows the situation where aperiodic SRS triggering is bundled with PUSCH.

[0063] Table 4

[0064] Therefore, DCI format 0_3 is not flexible enough and needs to be enhanced.

[0065] In the embodiments of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; for example, an RRC message, including, for example, an MIB, system information, or a dedicated RRC message; or an RRC information element (RRC IE). The high-layer signaling may also be, for example, MAC (Medium Access Control) signaling; or a MAC control element (MAC CE). However, the present application is not limited thereto.

[0066] In the following description, to avoid confusion, the terms "PDCCH" and "Physical Downlink Control Channel" or "downlink control information" are interchangeable, and the terms "PDSCH" and "Physical Downlink Data Channel" or "downlink data" are also interchangeable. Furthermore, transmitting or receiving a PDCCH can be understood as transmitting or receiving downlink control information carried by the PDCCH; transmitting or receiving a PDSCH can be understood as transmitting or receiving downlink data carried by the PDSCH.

[0067] Embodiments of the first aspect

[0068] The present invention provides a multi-carrier scheduling method, which is described from the perspective of a terminal device that can support 8-transmission (8Tx) uplink transmission. FIG2 is a schematic diagram of the multi-carrier scheduling method of the present invention. As shown in FIG2, the method includes:

[0069] 201, the terminal device receives downlink control information from the network device;

[0070] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0071] As shown in FIG2 , the method may further include:

[0072] 202. The terminal device performs uplink transmission and / or aperiodic sounding reference signal transmission (SRS transmission) in multiple cells according to the downlink control information.

[0073] It is worth noting that FIG2 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG2 above.

[0074] In some embodiments, the downlink control information is DCI format 0_3.

[0075] In some embodiments, uplink transmission on multiple cells scheduled by the downlink control information is up to 8 layers.

[0076] In some embodiments, the downlink control information includes two groups of MCS / NDI / RV fields to support up to 8 layers of uplink transmission; wherein the first group of MCS / NDI / RV fields is used for the first codeword, and the second group of MCS / NDI / RV fields is used for the second codeword.

[0077] For example, in DCI format 0_3, two sets of MCS / NDI / RV fields may be included to support up to 8-layer PUSCH transmission. The second set of MCS / NDI / RV fields in DCI format 0_3 is applied to the second codeword (or second transport block).

[0078] In some embodiments, the MCS field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponding to a modulation and coding scheme (MCS) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index;

[0079] The NDI field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponding to a new data indication (NDI) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index;

[0080] The RV field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponds to a redundancy version (RV) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

[0081] Figure 3 is a schematic diagram of DCI format 0_3 supporting up to 8-layer PUSCH transmission according to an embodiment of the present application. As shown in Figure 3, DCI format 0_3 may include a first set of MCS / NDI / RV fields, as shown by the first MCS, first NDI, and first RV in Figure 3; DCI format 0_3 may also include a second set of MCS / NDI / RV fields, as shown by the second MCS, second NDI, and second RV in Figure 3.

[0082] As shown in Figure 3, the second MCS includes multiple blocks (block#1 to block#N). Each block corresponds to the MCS of a scheduling cell, and these blocks are placed in ascending order of serving cell index. In one example, each block is 5 bits.

[0083] As shown in Figure 3, the second NDI includes multiple blocks (block#1 to block#N). Each block corresponds to a new data indicator of a scheduling cell, and these blocks are placed in ascending order of serving cell index. In one example, each block is 1 bit.

[0084] As shown in Figure 3, the second RV contains multiple blocks (block#1 to block#N). Each block corresponds to a redundant version of a scheduling cell, and these blocks are placed in ascending order of serving cell index. In one example, each block is 2 bits.

[0085] In some embodiments, at least one of the maximum rank (maxRank) or the maximum MIMO layer (maxMIMO-layer) across all scheduled cells is greater than 4, and the first group of MCS / NDI / RV domains and the second group of MCS / NDI / RV domains are both included in the downlink control information; the maximum rank (maxRank) or the maximum MIMO layer (maxMIMO-layer) across all scheduled cells is not greater than 4, and the second group of MCS / NDI / RV domains are not included in the downlink control information.

[0086] For example, if at least one of the values ​​of maxRank / maxMIMO layers on all scheduling CCs is greater than 4, both sets of MCS / NDI / RV fields are present in DCI format 0_3. If the values ​​of maxRank / maxMIMO layers on all scheduling CCs are not greater than 4, the second set of MCS / NDI / RV fields is not present in DCI format 0_3.

[0087] Table 5 is an example of DCI format 0_3 according to an embodiment of the present application, which schematically illustrates a situation where DCI format 0_3 supports up to 8 layers of PUSCH transmission.

[0088] Table 5

[0089] In some embodiments, a second group of MCS / NDI / RV fields is included in the downlink control information, and each block for each scheduled cell in the second group of MCS / NDI / RV fields exists; the MCS and RV of the corresponding transport block indicate whether a transport block is used for transmission on a cell.

[0090] For example, if the second set of MCS / NDI / RV fields exists, then each block of the MCS / NDI / RV fields for each scheduled CC should be present. Whether a transport block is used for transmission on a CC can be further indicated by the specific values ​​of the MCS and RV of the corresponding transport block. For example, if the MCS and RV set for a transport block on a CC are: MCS = 26 and RV = 1, the corresponding transport block is disabled.

[0091] In some embodiments, a second group of MCS / NDI / RV fields is included in the downlink control information, and whether a block for a scheduling cell in the second group of MCS / NDI / RV fields exists depends on the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the corresponding scheduling cell.

[0092] For example, if the second set of MCS / NDI / RV fields exists, whether a block of the second set of MCS / NDI / RV fields for a scheduling CC exists depends on the value of maxRank / maxMIMO layer of the corresponding scheduling CC.

[0093] In some embodiments, if the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the scheduling cell is greater than 4, the block for the scheduling cell in the second group of MCS / NDI / RV domains exists; if the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the scheduling cell is not greater than 4, the block for the scheduling cell in the second group of MCS / NDI / RV domains does not exist; whether a transport block is used for transmission on the scheduling cell is indicated by the MCS and RV of the corresponding transport block.

[0094] For example, if the maxRank / maxMIMO layers of the scheduling CC are greater than 4, then the second set of MCS / NDI / RV field blocks for the scheduling CC exists; otherwise, the block does not exist. If the second set of MCS / NDI / RV field blocks exists, the specific values ​​of the MCS and RV of the corresponding transport block can be used to further indicate whether a transport block is used for transmission on the scheduling CC, for example, MCS = 26 and RV = 1.

[0095] In some embodiments, regardless of whether the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) for one scheduling cell or for all scheduling cells is greater than 4, the first group of MCS / NDI / RV domains and the second group of MCS / NDI / RV domains are included in the downlink control information.

[0096] For example, the MCS / NDI / RV field should be present for each block of each scheduled CC. Whether a transport block is used for transmission on a CC can be further indicated by the specific values ​​of the MCS and RV of the corresponding transport block. For example, if the MCS and RV set for a transport block on a CC are: MCS = 26 and RV = 1, the corresponding transport block is disabled.

[0097] For another example, whether a block in the second set of MCS / NDI / RV fields for a scheduling CC exists depends on the maxRank / maxMIMO layer values ​​of the corresponding scheduling CC. If the maxRank / maxMIMO layer of the scheduling CC is greater than 4, then a block in the second set of MCS / NDI / RV fields for the scheduling CC exists; otherwise, the block does not exist. If a block in the second set of MCS / NDI / RV fields exists, the specific values ​​of the MCS and RV of the corresponding transport block can be used to further indicate whether a transport block is used for transmission on the scheduling CC, for example, MCS = 26 and RV = 1.

[0098] In some embodiments, the downlink control information includes a set of MCS / NDI / RV fields to support up to 8 layers of uplink transmission; wherein each block in the set of MCS / NDI / RV fields includes a first part and a second part, the first part is used for the first codeword, and the second part is used for the second codeword.

[0099] For example, DCI format 0_3 includes only one MCS / NDI / RV field. To support up to 8 layers of PUSCH transmission, each block of the MCS / NDI / RV field can be divided into two parts. The first part of the block is applied to one transport block, and the second part of the block is applied to another transport block.

[0100] For another example, if at least one of the values ​​of maxRank / maxMIMO layers on all scheduled CCs is greater than 4, each block of the MCS / NDI / RV domain is divided into two parts. If the values ​​of maxRank / maxMIMO layers on all scheduled CCs are not greater than 4, the blocks of the MCS / NDI / RV domain are not divided into two parts.

[0101] Alternatively, if the maxRank / maxMIMO layer value of a scheduling CC is greater than 4, the block of the MCS / NDI / RV field of the corresponding scheduling CC is divided into two parts. Otherwise, the block of the MCS / NDI / RV field of the corresponding scheduling CC is not divided into two parts.

[0102] In some embodiments, in the downlink control information, the triggering of the aperiodic SRS is decoupled from the PUSCH scheduled on the cell with the smallest index among the scheduled cells. The aperiodic SRS is triggered on one or more cells, and the PUSCH is avoided from being scheduled by setting the UL-SCH indicator to zero and the CSI request to all zeros. The aperiodic SRS is triggered by the downlink control information that does not schedule the PUSCH, and the TPC command included in the downlink control information is applied to the SRS transmission on the corresponding scheduled cell.

[0103] In some embodiments, based on the terminal device capability, decoupling of non-periodic SRS triggering and the PUSCH in the downlink control information is supported; the terminal device capability is applied to all scheduling cells; or, the terminal device capability is applied to a scheduling cell, and the decoupling of non-periodic SRS triggering and the PUSCH is cell-specific (cell-specific or CC specific).

[0104] For example, support for decoupling aperiodic SRS and PUSCH in DCI format 0_3 may depend on UE capabilities. UE capabilities may apply to all scheduled CCs. Alternatively, UE capabilities may apply to each scheduled CC, i.e., support for decoupling aperiodic SRS and PUSCH may be CC-specific.

[0105] Table 6 is an example of DCI format 0_3 of an embodiment of the present application, which schematically illustrates a case where aperiodic SRS and PUSCH decoupling are supported.

[0106] Table 6

[0107] In some embodiments, in the downlink control information, a CSI request field is used to trigger CSI-RS on one or more scheduling cells; the CSI request field includes multiple blocks, each block corresponds to a CSI request for a scheduling cell, and the multiple blocks are placed in ascending order of serving cell index.

[0108] For example, in DCI format 0_3, the CSI request field can be extended to trigger CSI-RS on one or more scheduling cells. The CSI request field contains multiple blocks, each corresponding to the CSI request of a scheduling cell, and these blocks are placed in ascending order of the serving cell index.

[0109] In some embodiments, in the downlink control information, an uplink shared channel indication (UL-SCH indicator) field is applied to multiple scheduled cells; the uplink shared channel indication field includes multiple blocks, each block corresponds to an uplink shared channel indication for a scheduled cell, and the multiple blocks are placed in ascending order of serving cell index.

[0110] For example, in DCI format 0_3, the UL-SCH indication field can be applied to all scheduled cells. Alternatively, the UL-SCH indication field is extended to multiple blocks. Each block corresponds to the UL-SCH indication of a scheduled cell, and these blocks are placed in ascending order of the serving cell index.

[0111] In some embodiments, in the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_1: precoding information and number of layers, antenna ports, PTRS and DMRS association.

[0112] For example, in DCI format 0_3, for a UE with 8Tx, the block size in one, several, or all of the following fields shall be at least consistent with the size of the corresponding field in DCI format 0_1:

[0113] -Precoding information and number of layers;

[0114] -Antenna ports;

[0115] -PTRS-DMRS association

[0116] -SRS resource indicator (SRI).

[0117] In some embodiments, in the downlink control information, a terminal device with 8Tx can be supported by a single codeword and / or a single transport block; the downlink control information supports PUSCH transmission with 8 antenna ports and a maximum number of layers is 4.

[0118] For example, in DCI format 0_3, the enhanced DMRS introduced in Rel-18 can be applied. For example, enhanced dmrs-type can be configured. If DCI format 0_3 supports single codeword / single transport block, up to four DMRS ports can be used for PUSCH scheduled by DCI format 0-3. If DCI format 0_3 supports dual codeword / dual transport block, up to eight DMRS ports can be used for PUSCH scheduled by DCI format 0-3.

[0119] For another example, the enhanced DMRS introduced in Rel-18 is not applied to DCI format 0_3.

[0120] In some embodiments, in the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_2: precoding information and number of layers, antenna port, PTRS and DMRS association, SRS resource indication.

[0121] For example, in DCI format 0_3, for a UE with 8Tx, the block size in one, several, or all of the following fields shall take the size of the corresponding field in DCI format 0_2 as a reference:

[0122] -Precoding information and number of layers;

[0123] -Antenna ports;

[0124] -PTRS-DMRS association

[0125] -SRS resource indicator (SRI).

[0126] Table 7 is an example of DCI format 0_3 of an embodiment of the present application, but the present application is not limited thereto.

[0127] Table 7

[0128] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0129] As can be seen from the above embodiments, downlink control information (eg, DCI format 0_3) can schedule PUSCH transmission with up to 8 layers. In addition, in DCI format 0_3, aperiodic SRS triggering can be decoupled from PUSCH scheduling, thereby increasing flexibility.

[0130] Embodiments of the second aspect

[0131] The embodiment of the present application provides a multi-carrier scheduling method, which is described from the perspective of a network device. The embodiment of the second aspect can be combined with the embodiment of the first aspect, and the same contents as the embodiment of the first aspect will not be repeated.

[0132] FIG4 is a schematic diagram of a multi-carrier scheduling method according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0133] 401, the network device sends downlink control information to the terminal device;

[0134] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0135] As shown in FIG4 , the method may further include:

[0136] 402. The terminal device performs uplink transmission and / or aperiodic sounding reference signal transmission (SRS transmission) in multiple cells according to the downlink control information.

[0137] It is worth noting that FIG4 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG4 above.

[0138] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0139] As can be seen from the above embodiments, downlink control information (eg, DCI format 0_3) can schedule PUSCH transmission with up to 8 layers. In addition, in DCI format 0_3, aperiodic SRS triggering can be decoupled from PUSCH scheduling, thereby increasing flexibility.

[0140] Embodiments of the third aspect

[0141] The embodiment of the present application provides a multi-carrier scheduling device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. The contents that are the same as those in the embodiment of the first aspect are not repeated here.

[0142] FIG5 is a schematic diagram of a multi-carrier scheduling apparatus according to an embodiment of the present application. As shown in FIG5 , the multi-carrier scheduling apparatus 500 includes:

[0143] A receiving unit 501, which receives downlink control information from a network device;

[0144] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0145] In some embodiments, as shown in FIG5 , the multi-carrier scheduling apparatus 500 may further include:

[0146] The transmitting unit 502 performs uplink transmission and / or aperiodic sounding reference signal transmission (SRS transmission) in multiple cells according to the downlink control information.

[0147] In some embodiments, the downlink control information is DCI format 0_3.

[0148] In some embodiments, uplink transmission on multiple cells scheduled by the downlink control information is up to 8 layers.

[0149] In some embodiments, the downlink control information includes two groups of MCS / NDI / RV fields to support up to 8 layers of uplink transmission; wherein the first group of MCS / NDI / RV fields is used for the first codeword, and the second group of MCS / NDI / RV fields is used for the second codeword.

[0150] In some embodiments, the MCS field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponding to a modulation and coding scheme (MCS) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

[0151] In some embodiments, the NDI field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponding to a new data indication (NDI) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

[0152] In some embodiments, the RV field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponding to a redundancy version (RV) for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

[0153] In some embodiments, at least one of the maximum rank (maxRank) or the maximum MIMO layer (maxMIMO-layer) across all scheduled cells is greater than 4, and the first group of MCS / NDI / RV domains and the second group of MCS / NDI / RV domains are both included in the downlink control information.

[0154] In some embodiments, the maximum rank (maxRank) or the maximum MIMO layer (maxMIMO-layer) across all scheduled cells is not greater than 4, and the second group of MCS / NDI / RV fields is not included in the downlink control information.

[0155] In some embodiments, the second group of MCS / NDI / RV fields is included in the downlink control information, and each block for each scheduled cell in the second group of MCS / NDI / RV fields exists.

[0156] In some embodiments, whether a transport block is used for transmission on a cell is indicated by the MCS and RV of the corresponding transport block.

[0157] In some embodiments, the second group of MCS / NDI / RV domains is included in the downlink control information, and whether a block for a scheduling cell in the second group of MCS / NDI / RV domains exists depends on the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the corresponding scheduling cell.

[0158] In some embodiments, the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the scheduling cell is greater than 4, then the block for the scheduling cell in the second group of MCS / NDI / RV fields exists.

[0159] In some embodiments, the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) of the scheduling cell is not greater than 4, then the block for the scheduling cell in the second group of MCS / NDI / RV domains does not exist.

[0160] In some embodiments, whether a transport block is used for transmission on the scheduling cell is indicated by the MCS and RV of the corresponding transport block.

[0161] In some embodiments, regardless of whether the maximum rank (maxRank) or maximum MIMO layer (maxMIMO-layer) for one scheduling cell or for all scheduling cells is greater than 4, the first group of MCS / NDI / RV domains and the second group of MCS / NDI / RV domains are both included in the downlink control information.

[0162] In some embodiments, the downlink control information includes a set of MCS / NDI / RV fields to support up to 8 layers of uplink transmission; wherein each block in the set of MCS / NDI / RV fields includes a first part and a second part, the first part is used for the first codeword, and the second part is used for the second codeword.

[0163] In some embodiments, in the downlink control information, the triggering of the aperiodic SRS is decoupled from the PUSCH scheduled on the cell with the smallest index among the scheduled cells.

[0164] In some embodiments, the aperiodic SRS is triggered on one or more cells and scheduling of the PUSCH is avoided by setting the UL-SCH indicator to zero and the CSI request to all zeros.

[0165] In some embodiments, the aperiodic SRS is triggered by the downlink control information that does not schedule a PUSCH, and a TPC command included in the downlink control information is applied to SRS transmission on a corresponding scheduling cell.

[0166] In some embodiments, based on the terminal device capability, decoupling of aperiodic SRS triggering and the PUSCH in the downlink control information is supported.

[0167] In some embodiments, the terminal device capability is applied to all scheduling cells; or, the terminal device capability is applied to one scheduling cell, and the decoupling of the aperiodic SRS triggering and the PUSCH is cell-specific (cell-specific or CC specific).

[0168] In some embodiments, in the downlink control information, the CSI request field is used to trigger CSI-RS on one or more scheduling cells.

[0169] In some embodiments, the CSI request field includes a plurality of blocks, each block corresponding to a CSI request for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

[0170] In some embodiments, in the downlink control information, an uplink shared channel indicator (UL-SCH indicator) field is applied to multiple scheduling cells.

[0171] In some embodiments, the uplink shared channel indicator field includes a plurality of blocks, each block corresponds to an uplink shared channel indicator for a scheduling cell, and the plurality of blocks are placed in ascending order of serving cell indexes.

[0172] In some embodiments, in the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_1: precoding information and number of layers, antenna ports, PTRS and DMRS association, SRS resource indication.

[0173] In some embodiments, in the downlink control information, a terminal device with 8Tx can be supported by a single codeword and / or a single transport block; the downlink control information supports PUSCH transmission with 8 antenna ports and a maximum number of layers is 4.

[0174] In some embodiments, in the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_2: precoding information and number of layers, antenna port, PTRS and DMRS association, SRS resource indication.

[0175] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0176] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-carrier scheduling apparatus 500 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0177] In addition, for simplicity, FIG5 only illustrates the connection relationship or signal path between various components or modules. However, those skilled in the art should be aware that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0178] As can be seen from the above embodiments, downlink control information (eg, DCI format 0_3) can schedule PUSCH transmission with up to 8 layers. In addition, in DCI format 0_3, aperiodic SRS triggering can be decoupled from PUSCH scheduling, thereby increasing flexibility.

[0179] Embodiments of the fourth aspect

[0180] The embodiment of the present application provides a multi-carrier scheduling device. The device may be, for example, a network device, or one or more components or assemblies configured in the network device. The contents that are the same as those in the first and second aspects of the embodiment are not repeated here.

[0181] FIG6 is a schematic diagram of a multi-carrier scheduling apparatus according to an embodiment of the present application. As shown in FIG6 , the multi-carrier scheduling apparatus 600 includes:

[0182] A sending unit 601, which sends downlink control information to a terminal device;

[0183] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0184] In some embodiments, as shown in FIG6 , the multi-carrier scheduling apparatus 600 may further include:

[0185] The receiving unit 602 receives uplink transmission and / or aperiodic sounding reference signal transmission (SRS transmission) performed by the terminal device in multiple cells according to the downlink control information.

[0186] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The multi-carrier scheduling apparatus 600 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0187] In addition, for the sake of simplicity, FIG6 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0188] As can be seen from the above embodiments, downlink control information (eg, DCI format 0_3) can schedule PUSCH transmission with up to 8 layers. In addition, in DCI format 0_3, aperiodic SRS triggering can be decoupled from PUSCH scheduling, thereby increasing flexibility.

[0189] Embodiments of the fifth aspect

[0190] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents that are the same as those in the first to fourth aspects of the embodiments will not be repeated.

[0191] In some embodiments, the communication system 100 may include at least:

[0192] A network device that sends downlink control information to a terminal device; the downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger aperiodic sounding reference signal transmission (SRS transmission) in the multiple cells;

[0193] A terminal device receives downlink control information from a network device.

[0194] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0195] Figure 7 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 7, network device 700 may include a processor 710 (e.g., a central processing unit (CPU)) and a memory 720; memory 720 is coupled to processor 710. Memory 720 may store various data and may also store an information processing program 730, which is executed under the control of processor 710.

[0196] For example, the processor 710 may be configured to execute a program to implement the multi-carrier scheduling method as described in the embodiment of the second aspect. For example, the processor 710 may be configured to perform the following control: sending downlink control information to a terminal device; wherein the downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger transmission of aperiodic sounding reference signals on the multiple cells.

[0197] In addition, as shown in Figure 7, network device 700 may further include: a transceiver 740 and an antenna 750; wherein, the functions of the above components are similar to those in the prior art and are not described here in detail. It is worth noting that network device 700 does not necessarily include all the components shown in Figure 7; in addition, network device 700 may also include components not shown in Figure 7, and reference may be made to the prior art for details.

[0198] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0199] Figure 8 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 8 , terminal device 800 may include a processor 810 and a memory 820. Memory 820 stores data and programs and is coupled to processor 810. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0200] For example, the processor 810 may be configured to execute a program to implement the multi-carrier scheduling method as described in the embodiment of the first aspect. For example, the processor 810 may be configured to perform the following control: receiving downlink control information from a network device; wherein the downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger transmission of aperiodic sounding reference signals on the multiple cells.

[0201] As shown in Figure 8 , the terminal device 800 may further include: a communication module 830, an input unit 840, a display 850, and a power supply 860. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 800 does not necessarily include all of the components shown in Figure 8 , and these components are not essential. Furthermore, the terminal device 800 may also include components not shown in Figure 8 , for which reference may be made to the prior art.

[0202] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the multi-carrier scheduling method described in the embodiment of the first aspect.

[0203] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the multi-carrier scheduling method described in the embodiment of the first aspect.

[0204] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program enables the network device to perform the multi-carrier scheduling method described in the embodiment of the second aspect.

[0205] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the multi-carrier scheduling method described in the embodiment of the second aspect.

[0206] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0207] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0208] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0209] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0210] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0211] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0212] 1. A multi-carrier scheduling method, applied to a terminal device capable of supporting 8-transmit (8Tx) uplink transmission, the method comprising:

[0213] The terminal device receives downlink control information from the network device;

[0214] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0215] 2. The method according to Note 1, wherein the downlink control information is DCI format 0_3.

[0216] 3. The method according to Note 2, wherein, in the downlink control information, a terminal device with 8Tx can be supported by a single codeword and / or a single transmission block; the downlink control information supports PUSCH transmission with 8 antenna ports and the maximum number of layers is 4.

[0217] 4. The method according to Note 2, wherein, in the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_2: precoding information and number of layers, antenna port, PTRS and DMRS association, SRS resource indication.

[0218] 5. A multi-carrier scheduling method, applied to a network device, comprising:

[0219] The network device sends downlink control information to the terminal device;

[0220] The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission (SRS transmission) in the multiple cells.

[0221] 6. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the multi-carrier scheduling method as described in Note 1.

[0222] 7. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the multi-carrier scheduling method as described in Note 5.

Claims

1. A multi-carrier scheduling device, configured in a terminal device capable of supporting 8Tx uplink transmission, the device comprising: A receiving unit, which receives downlink control information from a network device; The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

2. The device according to claim 1, wherein: The downlink control information is in DCI format 0_3; In the downlink control information, a terminal device with 8Tx can be supported by a single codeword and / or a single transmission block; the downlink control information supports PUSCH transmission with 8 antenna ports and a maximum number of layers is 4.

3. The device according to claim 1, wherein: The uplink transmission on multiple cells scheduled by the downlink control information may be up to 8 layers.

4. The device according to claim 3, wherein: The downlink control information includes two groups of MCS / NDI / RV fields to support up to 8 layers of uplink transmission; the first group of MCS / NDI / RV fields is used for the first codeword, and the second group of MCS / NDI / RV fields is used for the second codeword.

5. The device according to claim 4, wherein: The MCS field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponds to a modulation and coding scheme for a scheduled cell, and the plurality of blocks are placed according to an ascending order of a serving cell index; The NDI field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponds to a new data indication for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index; The RV field in the second set of MCS / NDI / RV fields includes a plurality of blocks, each block corresponds to a redundancy version for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

6. The device according to claim 4, wherein: At least one of the maximum rank or the maximum MIMO layer across all scheduled cells is greater than 4, and the first group of MCS / NDI / RV fields and the second group of MCS / NDI / RV fields are both included in the downlink control information; The maximum rank or maximum MIMO layer across all scheduled cells is not greater than 4, and the second group of MCS / NDI / RV domains is not included in the downlink control information.

7. The device according to claim 6, wherein: The second group of MCS / NDI / RV fields is included in the downlink control information, then each block for each scheduled cell in the second group of MCS / NDI / RV fields exists; Whether a transport block is used for transmission on a cell is indicated by the MCS and RV of the corresponding transport block.

8. The device according to claim 6, wherein: The second group of MCS / NDI / RV domains is included in the downlink control information, and whether a block for a scheduled cell in the second group of MCS / NDI / RV domains exists depends on the maximum rank or maximum MIMO layer of the corresponding scheduled cell.

9. The device according to claim 8, wherein: The maximum rank or maximum MIMO layer of the scheduled cell is greater than 4, then the block for the scheduled cell in the second group of MCS / NDI / RV fields exists; If the maximum rank or maximum MIMO layer of the scheduled cell is not greater than 4, the block for the scheduled cell in the second group of MCS / NDI / RV fields does not exist; Whether a transport block is used for transmission on the scheduling cell is indicated by the MCS and RV of the corresponding transport block.

10. The device according to claim 4, wherein: Regardless of whether the maximum rank or maximum MIMO layer for one scheduled cell or for all scheduled cells is greater than 4, the first group of MCS / NDI / RV domains and the second group of MCS / NDI / RV domains are included in the downlink control information.

11. The device according to claim 3, wherein: The downlink control information includes a set of MCS / NDI / RV domains to support up to 8 layers of uplink transmission; wherein each block in the set of MCS / NDI / RV domains includes a first part and a second part, the first part is used for a first codeword, and the second part is used for a second codeword.

12. The device according to claim 1, wherein: In the downlink control information, the triggering of the aperiodic SRS is decoupled from the PUSCH scheduled on the cell with the smallest index among the scheduled cells.

13. The device according to claim 12, wherein: The aperiodic SRS is triggered on one or more cells and avoids scheduling the PUSCH by setting the UL-SCH indicator to zero and the CSI request to all zeros.

14. The device according to claim 12, wherein: The aperiodic SRS is triggered by the downlink control information that does not schedule a PUSCH, and a TPC command included in the downlink control information is applied to SRS transmission on a corresponding scheduling cell.

15. The device according to claim 12, wherein: According to the terminal device capability, decoupling of aperiodic SRS triggering from the PUSCH in the downlink control information is supported; The terminal device capability is applied to all scheduling cells; or, the terminal device capability is applied to one scheduling cell, and the decoupling of the non-periodic SRS triggering and the PUSCH is cell-specific.

16. The device according to claim 1, wherein In the downlink control information, the CSI request field is used to trigger the CSI-RS on one or more scheduling cells; The CSI request domain includes a plurality of blocks, each block corresponds to a CSI request for a scheduling cell, and the plurality of blocks are placed according to an ascending order of a serving cell index.

17. The device according to claim 1, wherein: In the downlink control information, the uplink shared channel indication field is applied to multiple scheduling cells; The uplink shared channel indicator field includes a plurality of blocks, each block corresponds to an uplink shared channel indicator for a scheduled cell, and the plurality of blocks are placed in ascending order of serving cell indexes.

18. The device according to claim 1, wherein: In the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_1: precoding information and number of layers, antenna port, PTRS and DMRS association, SRS resource indication; or, In the downlink control information, the block size of at least one of the following fields is consistent with the size of the corresponding field of DCI format 0_2: precoding information and number of layers, antenna port, PTRS and DMRS association, SRS resource indication.

19. A multi-carrier scheduling device, configured in a network device, the device comprising: A sending unit, which sends downlink control information to a terminal device; The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger non-periodic sounding reference signal transmission in the multiple cells.

20. A communication system comprising: A network device that sends downlink control information to a terminal device; The downlink control information is used to schedule the terminal device to perform uplink transmission in multiple cells, and the downlink control information is used to trigger aperiodic sounding reference signal transmission in the multiple cells; A terminal device receives downlink control information from a network device.

Images