Shared channel scheduling method, device, terminal and network side equipment

Abstract

The present application discloses a shared channel scheduling method, apparatus, terminal and network-side equipment, which belongs to the field of communication technology. The shared channel scheduling method of an embodiment of the present application includes: a terminal receives first downlink control information DCI, the first DCI is used to schedule the transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel; wherein the scheduling information includes at least one of the following: time domain resource allocation information corresponding to the at least one shared channel, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB binding size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI‑RS trigger information and non-numerical feedback time offset.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a shared channel scheduling method, apparatus, terminal, and network-side equipment. Background Art

[0002] During the research on the Rel-17 52.6~71GHz characteristics, it was confirmed that new subcarrier spacing (SCS), including 480kHz and 960kHz, need to be introduced for the new New Radio (NR) deployment frequency band. For these newly introduced SCS, the physical downlink control channel (PDCCH) monitoring needs to be adjusted or enhanced accordingly, for example, to avoid the user equipment (UE, also known as the terminal) from needing to monitor the PDCCH in each slot (very short duration) to reduce the complexity of UE implementation. Accordingly, in order to make full use of carrier time domain resources, it is necessary to study / introduce multi-physical downlink shared channel (Multi-Physical Downlink Shared Channel, Multi-PDSCH) scheduling and multi-physical uplink shared channel (Multi-Physical Uplink Shared Channel, Multi-PUSCH) scheduling.

[0003] Multi-PDSCH scheduling means that a single downlink control information (DCI) can schedule multiple PDSCH transmissions on the same carrier at one time. According to the NR protocol, these PDSCHs do not overlap in the time domain.

[0004] For Multi-PDSCH scheduling, there are still some scheduling details that have not been discussed and corresponding solutions have not been formed, which affects the practical application of Multi-PDSCH scheduling. Summary of the invention

[0005] The embodiments of the present application provide a shared channel scheduling method, apparatus, terminal and network-side equipment, which can solve the problem that there is no complete solution for the configuration and indication of Multi-PDSCH scheduling in the prior art, which affects the practical application of Multi-PDSCH scheduling.

[0006] In a first aspect, a shared channel scheduling method is provided, including:

[0007] The terminal receives first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0008] The scheduling information includes at least one of the following:

[0009] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0010] In a second aspect, a shared channel scheduling method is provided, including:

[0011] The network side device sends first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0012] The scheduling information includes at least one of the following:

[0013] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0014] In a third aspect, a shared channel scheduling device is provided, including:

[0015] A receiving module, configured to receive first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0016] The scheduling information includes at least one of the following:

[0017] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0018] In a fourth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0019] In a fifth aspect, a terminal is provided, including a processor and a communication interface, wherein the communication interface is used to receive first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0020] The scheduling information includes at least one of the following:

[0021] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0022] In a sixth aspect, a shared channel scheduling device is provided, including:

[0023] A sending module, configured to send first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0024] The scheduling information includes at least one of the following:

[0025] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0026] In the seventh aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the second aspect.

[0027] In an eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first downlink control information DCI, the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0028] The scheduling information includes at least one of the following:

[0029] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0030] In a ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0031] In the tenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect or the second aspect.

[0032] In the eleventh aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the second aspect.

[0033] In an embodiment of the present application, by including scheduling information for at least one shared channel in the first DCI for scheduling the transmission of at least one shared channel, at least one of the codeword indication information of multiple shared channels, VRB to PRB mapping information, PRB bundling size indication information, rate matching indication information, ZP CSI-RS trigger information and non-numerical feedback time offset is limited, so as to ensure that the actual application of scheduling of multiple shared channels is not affected. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0035] Figure 2 This is one of the flow charts of the shared channel scheduling method according to an embodiment of the present application;

[0036] Figure 3 This is one of the module schematic diagrams of the shared channel scheduling device according to an embodiment of the present application;

[0037] Figure 4 is a structural block diagram of a terminal in an embodiment of the present application;

[0038] Figure 5 This is a second flow chart of the shared channel scheduling method according to an embodiment of the present application;

[0039] Figure 6 This is the second module schematic diagram of the shared channel scheduling device according to an embodiment of the present application;

[0040] Figure 7 is a structural block diagram of a network side device in an embodiment of the present application;

[0041] Figure 8 It is a structural block diagram of the communication device of an embodiment of the present application. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0043] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0044] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned systems and radio technologies as well as for other systems and radio technologies. The following description describes a new radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system.

[0045] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a smart watch, a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, 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 B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0046] The shared channel scheduling method, apparatus, terminal and network side equipment provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0047] like Figure 2 As shown, an embodiment of the present application provides a shared channel scheduling method, including:

[0048] Step 201: The terminal receives first downlink control information DCI;

[0049] The first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0050] Optionally, the scheduling information includes but is not limited to at least one of the following:

[0051] The at least one shared channel includes time domain resource allocation information, codeword indication information, virtual resource block (VRB) to physical resource block (PRB) mapping information, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal (Zero Power Channel State Information Reference Signal, ZP CSI-RS) trigger information and non-numerical feedback time offset.

[0052] It should be noted that the first DCI mentioned in the embodiment of the present application can schedule both the physical uplink shared channel (PUSCH) and the physical downlink shared channel (PDSCH), that is, the shared channels mentioned above include PDSCH and / or PUSCH.

[0053] It should be noted here that the first DCI refers to a DCI sent by a network side device to a terminal for scheduling a shared channel.

[0054] Optionally, before the terminal receives the first DCI sent by the network side device, the network side device needs to first configure a time domain resource allocation table (TDRA Table) and send the configuration information of the time domain resource allocation table to the terminal. Optionally, the network side device uses the configuration information of the time domain resource allocation table to configure the target row in the time domain resource allocation table (it should be noted that the target row is any row in the time domain resource allocation table), and the configuration rule of the target row includes any of the following:

[0055] A11, each time domain resource allocation record in the target row corresponds to a transmission time offset;

[0056] The time domain resource allocation record here may be understood as indicating resources allocated in the time domain to a single scheduled shared channel, such as a set of occupied symbols.

[0057] The transmission time offset here can be understood as the time offset between each shared channel and the first DCI when the first DCI indicates the target row to schedule the shared channels corresponding to each time domain resource allocation record in this target row at one time, for example, the offset between the time unit in which each shared channel is located relative to the time unit in which the first DCI is transmitted, and the granularity is a time unit, such as a time slot.

[0058] It can be understood that, under this configuration, a gap at the time slot level or the symbol level is allowed to exist between symbol sets corresponding to adjacent time domain resource allocation records.

[0059] A12. Each time domain resource allocation record subset in the target row corresponds to a transmission time offset;

[0060] It should be noted that under this configuration method, when configuring each row in the time domain resource allocation table, one or more transmission time offsets can be configured, and each transmission time offset is further configured with one or more time domain resource allocation records and associated information, for example, mapping type (Mapping type), and the symbol set corresponding to the one or more time domain resource allocation records corresponding to each transmission time offset is required to be continuous or discontinuous (there may be a symbol-level Gap at this time).

[0061] It should be noted here that since the time domain resource allocation table usually contains multiple rows, when the network side device is configured, all rows in a time domain resource allocation table adopt the same or different configuration methods. For example, the time domain resource allocation table contains 10 rows, and these 10 rows are all configured in A11, or all configured in A12, or some of the 10 rows are configured in A11, and the other rows are configured in A12.

[0062] Optionally, the above-mentioned time domain resource allocation record may be a start length indication (SLIV) record.

[0063] It should also be noted that, for multi-PDSCH scheduling, the above transmission time offset can be represented by K0, and for PUSCH scheduling, the above transmission time offset can be represented by K2.

[0064] The different parameters included in the scheduling information are described in detail below.

[0065] 1. Scheduling information includes codeword indication information

[0066] It should be noted that, when dual codeword transmission is allowed, the indication of the codeword indication information satisfies any of the following:

[0067] B11, using an independent indication field to indicate the enabling state of each codeword;

[0068] It should be noted that this situation refers to introducing a new field in the first DCI to directly indicate the enabling status of each codeword. For example, a new indication bit may be introduced, or bits of an existing indication field may be reused.

[0069] Optionally, in this case, the indication of the codeword indication information satisfies one of the following:

[0070] B111, the independent indication field is used to indicate the enabling state of each codeword of at least one shared channel scheduled by the first DCI;

[0071] It should be noted that in order to reduce the indication overhead, a unified indication can be provided for each scheduled shared channel, that is, a single indication in the first DCI is applied to each shared channel scheduled by the first DCI. For example, a unified indication can be provided for each scheduled PDSCH, that is, a single indication in the first DCI is applied to each PDSCH scheduled by the first DCI. In other words, at this time, the independent indication field is used to indicate the enabling status of each codeword of all shared channels scheduled by the first DCI.

[0072] For example, in this case, different bits may be used to indicate the enabling status of each transport block (TB, such as TB1 and TB2), respectively, and applied to each PDSCH scheduled by the first DCI at the same time.

[0073] B112, the independent indication field respectively indicates the enabling state of each codeword of each shared channel scheduled by the first DCI;

[0074] It should be noted that in order to improve the flexibility of indication, each shared channel can also be indicated separately. For example, if the first DCI schedules two PDSCHs, the first DCI includes two independent indication fields, each of which is used to indicate the enable status of each codeword of a PDSCH.

[0075] B12. Use a first value combination of the first indication field to indicate an enable state of each codeword;

[0076] It should be noted that in this case, a specific value combination of the existing indication field is used for indication, that is, the first indication field is the indication field already used in the existing first DCI, for example, a value combination in the existing indication field that does not represent other indication meanings is used to indicate the enablement state of each codeword. In this way, the codeword enablement state can be determined for each scheduled shared channel.

[0077] Optionally, in this case, the enabling state of each codeword may be determined using one of the following rules:

[0078] B121. When each TB of each shared channel scheduled by the first DCI corresponds to two redundant version (RV) indication bits, if the first modulation and coding strategy (MCS) index corresponding to the first target TB is a preset MCS index and the first RV index corresponding to the first target TB is a preset RV index, it is determined that the first target TB is in a non-enabled state;

[0079] It should be noted that the first target TB mentioned in the embodiment of the present application refers to any TB corresponding to any shared channel scheduled by the first DCI; the RV index refers to the RV number, such as the RV ID (identifier).

[0080] That is to say, when each TB of each scheduled shared channel corresponds to two RV indication bits, the existing mechanism can be used, that is, when the first MCS index corresponding to the first target TB is 26 and the first RV index corresponding to the first target TB is 1, the first target TB is turned off, that is, the first target TB is in a disabled state.

[0081] It should be noted here that, based on current technology, for example, only when the DCI only schedules a single PDSCH, this PDSCH (the first TB) corresponds to two RV indication bits, otherwise each scheduled PDSCH (the first TB) only corresponds to a single RV indication bit.

[0082] B122. When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is a preset MCS index and the second RV index corresponding to the second target TB is one of the two RV index values ​​corresponding to the one RV indication bit, determine that the second target TB is in a disabled state;

[0083] It should be noted that the second target TB mentioned in the embodiment of the present application refers to any TB corresponding to any shared channel scheduled by the first DCI; the RV index refers to the RV number.

[0084] That is to say, when each TB of each shared channel scheduled corresponds to an RV indication bit, the first MCS index corresponding to the first target TB is 26, and the first RV index corresponding to the first target TB is one of the two RV index values ​​corresponding to the RV indication bit (for example, the first RV index corresponding to the first target TB is 2), the first target TB is turned off, that is, the first target TB is in a disabled state.

[0085] It should be noted that for NR-U Rel-16 Multi-PUSCH scheduling, when each PUSCH corresponds to a single RV indication bit, the RV index (rv id ) can only be 0 or 2, as shown in Table 1. If Multi-PDSCH scheduling continues to use this mechanism, it is necessary to adjust rv id The value of .

[0086] Table 1 Correspondence between RV index and value

[0087]

[0088] B123. When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the third MCS index corresponding to the third target TB is a preset MCS index and the third RV index corresponding to the third target TB is one of the two RV index values ​​corresponding to the one RV indication bit, and the value of the second indication field corresponding to the third target TB meets a preset condition, it is determined that the third target TB is in a disabled state;

[0089] It should be noted that the third target TB mentioned in the embodiment of the present application refers to any TB corresponding to any shared channel scheduled by the first DCI; the RV index refers to the RV number.

[0090] Optionally, the second indication field includes a new data indication (NDI) indication field corresponding to the third target TB, and the preset condition includes one of the following:

[0091] B1231, the NDI indication field is a preset value;

[0092] B1232: The value of the NDI indication field is flipped or not flipped relative to the NDI value before the first HARQ process;

[0093] It should be noted that the first HARQ process is the HARQ process occupied by the shared channel corresponding to the third target TB.

[0094] It should also be noted here that, for example, when the shared channel is PDSCH, when the terminal indicates or determines the codeword enablement status for each scheduled PDSCH, assuming that the antenna port (Antenna port(s)) indicated in the DCI is applied to each PDSCH scheduled by the DCI, then for each PDSCH, the terminal can determine its transmission properties based on the enablement status (i.e., on / off status) of its two codewords, including the occupied demodulation reference signal port (DMRS port) set, etc.

[0095] Optionally, whether the dual codeword transmission is allowed may be notified to the terminal in advance by the network side device, for example, configured to the terminal based on high-layer signaling.

[0096] Optionally, when dual codeword transmission is allowed, the maximum number of shared channels that can be simultaneously scheduled by a single DCI can be further restricted. For example, assuming that when only single codeword transmission is supported, the maximum number of shared channels that can be scheduled by a single DCI is M (hereinafter referred to as the single codeword maximum value), then when dual codeword transmission is allowed, the maximum number of shared channels that can be scheduled by a single DCI is M / 2, or M / 2 is further rounded up or down as the maximum number of shared channels that can be scheduled by a single DCI, which can be referred to as the dual codeword maximum value. Optionally, this can be achieved by limiting the configuration of the time domain resource allocation table. For example, when the high-level signaling configuration allows dual codeword transmission, in the time domain resource allocation table corresponding to the DCI that can be used to schedule multiple shared channel transmissions, the number of time domain resource allocation information configured in any row cannot exceed the above-mentioned dual codeword maximum value, and a certain time domain resource allocation information in a certain row can correspond one-to-one to a certain shared channel (it can be understood that when the high-level signaling configuration only allows single codeword transmission, these restrictions can still be used, except that the dual codeword maximum value is replaced by the single codeword maximum value).

[0097] 2. Scheduling information includes mapping information from VRB to PRB

[0098] It should be noted that when the terminal supports resource allocation type 1 and supports interleaved VRB-to-PRB mapping, the indication of the VRB-to-PRB mapping information includes the following:

[0099] C11. The first DCI includes multiple indication fields, each of which indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel;

[0100] Optionally, in this case, there is a corresponding indication field for each schedulable shared channel, for example, the indication field contains 1 bit.

[0101] C12. The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set;

[0102] That is, in this case, a single indication field is used to indicate the VRB-to-PRB mapping information of a single shared channel in the shared channel set scheduled by the first DCI.

[0103] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0104] Furthermore, in this case, other shared channels scheduled by the first DCI adopt a predefined mapping manner, and the predefined mapping manner may be specified by a protocol or configured based on a high-level signaling.

[0105] C13. The first DCI includes an indication field, and the VRB to PRB mapping information indicated by the indication field is applied to each scheduled shared channel;

[0106] It should be noted that this situation refers to using a single indication field to indicate the mapping information from VRB to PRB of each shared channel scheduled.

[0107] Optionally, whether the terminal supports resource allocation type 1, or whether it supports interleaving-based VRB to PRB mapping, may be notified in advance by the network side device to the terminal, for example, configured to the terminal based on high-layer signaling.

[0108] 3. Scheduling information includes PRB bundling size indication information

[0109] It should be noted that, when dynamic PRB bundling is adopted (for example, when the high-level parameter PRB bundling type configured by the network side device is set to dynamic binding), the indication of the PRB bundling size indication information includes the following:

[0110] D11. The first DCI includes multiple indication fields, each of which indicates the PRB bundling size corresponding to a scheduled shared channel;

[0111] Optionally, in this case, there is a corresponding indication field for each schedulable shared channel, for example, the indication field contains 1 bit.

[0112] D12. The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set;

[0113] That is, in this case, a single indication field is used to indicate the PRB bundling size indication information of a single shared channel in the shared channel set scheduled by the first DCI.

[0114] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0115] Furthermore, in this case, other shared channels scheduled by the first DCI adopt a predefined precoding granularity, and the predefined precoding granularity may be specified by a protocol or configured based on a high-level signaling.

[0116] D13. The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel;

[0117] It should be noted that this situation refers to applying a single indication field to indicate the PRB bundling size of each scheduled shared channel.

[0118] 4. Scheduling Information Includes Rate Matching Indication Information

[0119] It should be noted that, when it is necessary to dynamically indicate whether the resource set corresponding to rate matching style group 1 (rateMatchPatternGroup1) and / or rate matching style group 2 (rateMatchPatternGroup2) can be used for shared channel transmission (for example, when the configuration of high-level parameters rateMatchPatternGroup1 and rateMatchPatternGroup2 configured by the network side device is based on, it is necessary to indicate in DCI format 1_1 whether the resource set corresponding to each configured rate matching style group can be used for PDSCH transmission), the indication of the rate matching indication information includes the following:

[0120] E11. The first DCI includes multiple indication fields, each of which indicates the rate matching indication information corresponding to a scheduled shared channel;

[0121] Optionally, in this case, there is a corresponding indication field for each schedulable shared channel. For example, the indication field contains 1 bit or 2 bits, and each bit indicates whether the resource collection corresponding to the corresponding rate matching style group can be used for scheduled shared channel transmission. When it is 1 bit, this bit corresponds to rate matching style group one; when it is 2 bits, each bit corresponds to rate matching style group one and rate matching style group two respectively.

[0122] E12. The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set;

[0123] That is, in this case, a single indication field is used to indicate rate matching indication information of a single shared channel in the shared channel set scheduled by the first DCI.

[0124] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0125] Furthermore, in this case, other shared channels scheduled by the first DCI adopt a predefined resource availability assumption, which may be specified by the protocol or configured based on high-level signaling. For example, the relevant provisions for shared channels (such as PDSCH) scheduled by DCI format 1_0 may be followed, and the resource collection indicated by all Groups (i.e., rate matching style groups, which may be 0 / 1 / 2 based on the configuration of high-level parameters rateMatchPatternGroup1 and rateMatchPatternGroup2) are not available during shared channel transmission.

[0126] E13. The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel;

[0127] It should be noted that this situation refers to applying a single indication field to indicate the rate matching indication information of each shared channel scheduled.

[0128] 5. Scheduling information includes ZP CSI-RS trigger information

[0129] It should be noted that, when an aperiodic ZP CSI-RS resource set (aperiodic ZP CSI-RSresource set) needs to be dynamically indicated (for example, when the number of aperiodic ZP CSI-RSresource sets configured by the network side device based on high-level signaling is greater than 0), the indication of the ZP CSI-RS trigger information includes the following:

[0130] The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following:

[0131] F11, a target shared channel in the scheduled shared channel set;

[0132] That is, in this case, a single indication field indicates the ZP CSI-RS triggering information of a single shared channel in the shared channel set scheduled by the first DCI.

[0133] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0134] Further, in this case, other shared channels scheduled by the first DCI adopt a predefined triggering assumption, which may be specified by a protocol or configured based on a high-level signaling, for example, assuming that no aperiodic ZP CSI-RS resourceset is triggered.

[0135] F12, a target time unit among the time units occupied by the scheduled shared channel set;

[0136] That is, in this case, the single indication field indicates the ZP CSI-RS triggering information of a single time unit in the time units occupied by the shared channel set scheduled by the first DCI.

[0137] Optionally, the target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI. At this time, all shared channels transmitted within this time unit take into account the influence of the aperiodic ZP CSI-RS resource set triggering situation of a single indication domain.

[0138] Furthermore, in this case, other time units in the time units occupied by the shared channel set scheduled by the first DCI adopt predefined triggering assumptions, which may be specified by the protocol or configured based on high-level signaling. For example, it is assumed that no aperiodic ZP CSI-RS resource set is triggered. At this time, all shared channels transmitted in these time units will not be affected by the aperiodic ZP CSI-RS.

[0139] F13, each shared channel scheduled;

[0140] That is, in this case, a single indication field indicates the ZP CSI-RS triggering information of all shared channels scheduled by the first DCI.

[0141] F14, each time unit in the time units occupied by the scheduled shared channel set;

[0142] That is, in this case, a single indication field indicates the ZP CSI-RS triggering information of each time unit occupied by the shared channel set scheduled by the first DCI.

[0143] It should be noted that the methods of F13 and F14 can be understood as the solution for multi-slot PDSCH scheduling (Multi-slot PDSCH scheduling) in Rel-15 / 16.

[0144] It should be noted that the time unit mentioned above can be a time slot (Slot) or a sub-slot (Sub-slot), or other predefined unit duration, such as milliseconds (ms), or a predefined number of time slots or sub-slots, and no limitation is made here.

[0145] 6. Scheduling information includes non-numerical feedback time offset (can be represented by NNK1)

[0146] It should be noted that when a single DCI schedules one or more shared channels for transmission, a non-numerical feedback time offset can be indicated. Furthermore, a non-numerical feedback time offset can be indicated for a certain shared channel subset in a shared channel set consisting of one to multiple shared channels scheduled by a single DCI; at this time, it can be understood that the corresponding rules / mechanisms of the non-numerical feedback time offset are applied to the above-mentioned single shared channel, or each shared channel in the shared channel set / subset.

[0147] It should be noted that in this case, for a target HARQ process that does not provide an available hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback time, the terminal follows one of the following usage restriction methods:

[0148] G11. Before the network side device provides an available HARQ-ACK feedback time for the target HARQ process, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission;

[0149] This restriction method can be understood as: before the network side device provides the target HARQ process with available HARQ-ACK feedback time, no new shared channel transmission is scheduled or configured for the target HARQ process; that is, if a new shared channel transmission is scheduled or configured for the target HARQ process before the network side device provides the target HARQ process with available HARQ-ACK feedback time, it is considered an error case.

[0150] That is to say, in this case, if the network side device has not given a specific HARQ-ACK feedback time for this HARQ process / the shared channel transmission corresponding to this HARQ process, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission, that is, the target HARQ process cannot be scheduled with a new shared channel transmission, or there cannot be a configured shared channel transmission (for example, downlink semi-persistent scheduling (SPS) PDSCH transmission) to occupy the target HARQ process, which can also be understood as the target HARQ process being in a suspended state and cannot be further occupied. Optionally, the network must give a specific HARQ-ACK feedback time for this HARQ process / PDSCH transmission to ensure the normal occupancy of the HARQ process.

[0151] The usable HARQ-ACK feedback time, available HARQ-ACK feedback time or specific HARQ-ACK feedback time here can all be understood as a legal HARQ-ACK feedback time, and the time unit where the HARQ-ACK feedback is located can be determined based on this HARQ-ACK feedback time, and the corresponding HARQ-ACK is included in the HARQ-ACK codebook transmitted within this time unit and sent to the network side device. The legal HARQ-ACK feedback time can, optionally, be reflected as a time offset with a non-negative integer value, which is used to determine the time unit where the HARQ-ACK feedback is located. Optionally, the non-numerical feedback time offset (or NNK1) can actually be reflected in the specification as a time offset with a negative value, which is actually not usable, for example, reflected as -1.

[0152] G12. Before the network side device provides available HARQ-ACK feedback time for the target HARQ process, when the first condition is not met, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission;

[0153] This restriction method can be understood as: before the network side device provides the target HARQ process with available HARQ-ACK feedback time, when the first condition is not met, no new shared channel transmission is scheduled or configured for the target HARQ process; that is, if before the network side device provides the target HARQ process with available HARQ-ACK feedback time, when the first condition is not met, if a new shared channel transmission is scheduled or configured for the target HARQ process, it is considered an error case.

[0154] That is to say, in this case, if the network side device has not given a specific HARQ-ACK feedback time for this HARQ process / the shared channel transmission corresponding to this HARQ process, when the first condition is not met, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission (that is, the network is not allowed to make such scheduling or configuration), but when the first condition is met or after the first condition is met, the target HARQ process can be allowed to be scheduled or configured with a new shared channel transmission, that is, the network side device can schedule or configure a new shared channel transmission for the target HARQ process, and the terminal performs the corresponding receiving operation.

[0155] Optionally, there is no restriction on whether the network side device schedules or configures a new shared channel transmission for the target HARQ process to meet the above first condition, but when the new shared channel transmission scheduled or configured for the target HARQ process does not meet the above first condition, the terminal can ignore this new shared channel transmission.

[0156] Optionally, the first condition is that the start time of the new shared channel transmission scheduled or configured by the target HARQ process is located after the transmission end time of the first shared channel transmission, or is located after the end time of the first shared channel transmission is offset by a predefined time offset (this case means that the start time of the new shared channel transmission scheduled or configured by the target HARQ process is located after the end time of the first shared channel transmission plus the predefined time offset corresponding to the time);

[0157] The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

[0158] The predefined time offset here can be specified by the protocol or configured based on high-level signaling. The setting of the predefined time offset can take into account the PDSCH decoding time, or be determined based on N1 in the specification. Here, N1 can be understood as the minimum time interval between the end time of the PDSCH and the uplink transmission of the HARQ-ACK corresponding to the PDSCH, and the granularity can be a symbol.

[0159] It should also be noted that, for example, when the network side device gives a specific HARQ-ACK feedback time for a HARQ process / PDSCH transmission corresponding to the HARQ process, this HARQ process must be further scheduled or configured with a new shared channel transmission (for example, a new PDSCH transmission is scheduled, or a new SPS PDSCH transmission is configured) after the moment corresponding to the specific HARQ-ACK feedback time given by the network side device (for the last time).

[0160] It should be noted that the above description is for the case where the network side device may not provide a specific HARQ-ACK feedback time for the target HARQ process / the shared channel transmission corresponding to the target HARQ process.

[0161] Optionally, for a HARQ process or shared channel transmission (occupying a certain HARQ process, ie corresponding to this HARQ process) indicating NNK1 or unavailable HARQ-ACK feedback time, when a specific HARQ-ACK feedback time is given for it, the corresponding operation in Rel-16 may be used, including one of the following:

[0162] G21. When a dynamic codebook is used, the next downlink scheduling DCI (scheduling other HARQ processes) (and not indicating NNK1) may provide a specific HARQ-ACK feedback time for the shared channel transmission corresponding to this HARQ process / HARQ process (i.e., the corresponding HARQ-ACK is fed back in the UL slot / sub-slot indicated by this next downlink scheduling DCI);

[0163] G22. When the enhanced dynamic codebook is used, the next downlink scheduling DCI (which schedules other HARQ processes and) schedules or triggers the current shared channel group (and does not indicate NNK1) may give a specific HARQ-ACK feedback time for the shared channel transmission corresponding to this HARQ process / HARQ process (i.e., the corresponding HARQ-ACK is fed back in the UL slot / sub-slot indicated by the next downlink scheduling DCI);

[0164] The current shared channel group here is the shared channel group to which the shared channel transmission corresponding to this HARQ process belongs, such as PDSCH (group) group. Scheduling the current shared channel group here can be understood as the shared channel transmission scheduled by the next downlink scheduling DCI and this shared channel transmission belong to the same shared channel group. Triggering the current shared channel group here can be understood as triggering the HARQ-ACK feedback corresponding to the current shared channel group in the next downlink scheduling DCI.

[0165] G23. For any configured codebook type, the next DCI format that triggers the Type-3 codebook (NNK1 indication is not allowed) can give a specific HARQ-ACK feedback time (i.e., the corresponding HARQ-ACK is fed back within the UL slot / sub-slot indicated by this DCI format).

[0166] This HARQ process can be further scheduled or configured with new shared channel transmission only after the time corresponding to the specific HARQ-ACK feedback time given by the network side device (for the last time).

[0167] It should be noted that the embodiments of the present application provide corresponding solutions for time domain resource allocation, codeword indication, resource allocation related indication field, non-numerical feedback time offset, etc. of Multi-PDSCH / Multi-PUSCH scheduling, thereby ensuring that the Multi-PDSCH / Multi-PUSCH scheduling scheme is feasible and can achieve the purpose of reducing signaling overhead and / or improving scheduling flexibility.

[0168] It should be noted that the shared channel scheduling method provided in the embodiment of the present application can be executed by a shared channel scheduling device, or a control module in the shared channel scheduling device for executing the shared channel scheduling method. In the embodiment of the present application, the shared channel scheduling device provided in the embodiment of the present application is described by taking the execution of the shared channel scheduling method by the shared channel scheduling device as an example.

[0169] like Figure 3 As shown, the embodiment of the present application provides a shared channel scheduling device 300, including:

[0170] A receiving module 301 is configured to receive first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0171] The scheduling information includes at least one of the following:

[0172] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0173] Optionally, before the receiving module 301 receives the first downlink control information DCI, the method further includes:

[0174] A configuration receiving module is used to receive configuration information of a time domain resource allocation table from a network side device;

[0175] The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following:

[0176] Each time domain resource allocation record in the target row corresponds to a transmission time offset;

[0177] Each time domain resource allocation record subset in the target row corresponds to a transmission time offset;

[0178] The target row is any row in the time domain resource allocation table.

[0179] Optionally, when dual codeword transmission is allowed, the indication of the codeword indication information satisfies any one of the following:

[0180] Use an independent indication field to indicate the enable status of each codeword;

[0181] The first value combination of the first indication field is used to indicate the enabling state of each codeword.

[0182] Optionally, when an independent indication field is used to indicate the enable state of each codeword, the indication of the codeword indication information satisfies one of the following:

[0183] The independent indication field is used to indicate the enabling state of each codeword of at least one shared channel scheduled by the first DCI;

[0184] The independent indication field respectively indicates the enabling status of each codeword of each shared channel scheduled by the first DCI.

[0185] Optionally, when the first value combination of the first indication field is used to indicate the enable state of each codeword, the enable state of each codeword is determined using one of the following rules:

[0186] When each transport block TB of each shared channel scheduled by the first DCI corresponds to two redundant version RV indication bits, if the first modulation and coding strategy MCS index corresponding to the first target TB is a preset MCS index and the first RV index corresponding to the first target TB is a preset RV index, it is determined that the first target TB is in a disabled state;

[0187] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is a preset MCS index and the second RV index corresponding to the second target TB is one of the two RV index values ​​corresponding to the one RV indication bit, it is determined that the second target TB is in a disabled state;

[0188] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the third MCS index corresponding to the third target TB is a preset MCS index and the third RV index corresponding to the third target TB is one of the two RV index values ​​corresponding to the one RV indication bit, and the value of the second indication field corresponding to the third target TB meets a preset condition, it is determined that the third target TB is in a disabled state;

[0189] Among them, the first target TB, the second target TB, and the third target TB are any TBs corresponding to any shared channel scheduled by the first DCI.

[0190] Optionally, the second indication field includes a new data indication NDI indication field corresponding to the third target TB, and the preset condition includes one of the following:

[0191] The NDI indication field is a preset value;

[0192] The value of the NDI indication field is flipped or not flipped relative to the NDI value before the first HARQ process, and the first HARQ process is the HARQ process occupied by the shared channel corresponding to the third target TB.

[0193] Optionally, when the terminal supports resource allocation type 1 and supports interleaving-based VRB-to-PRB mapping, the indication of the VRB-to-PRB mapping information includes one of the following:

[0194] The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel;

[0195] The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set;

[0196] The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

[0197] Optionally, when dynamic PRB bundling is adopted, the indication of the PRB bundling size indication information includes one of the following:

[0198] The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel;

[0199] The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set;

[0200] The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

[0201] Optionally, in the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the indication of the rate matching indication information includes one of the following:

[0202] The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel;

[0203] The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set;

[0204] The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

[0205] Optionally, in the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the indication of the ZP CSI-RS triggering information includes one of the following:

[0206] The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following:

[0207] a target shared channel in a set of scheduled shared channels;

[0208] a target time unit among the time units occupied by the scheduled shared channel set;

[0209] Each shared channel scheduled;

[0210] Each time unit in the time units occupied by the scheduled shared channel set.

[0211] Optionally, the target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

[0212] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0213] Optionally, in a case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process for which an available hybrid automatic repeat request answer HARQ-ACK feedback time is not provided, the terminal follows one of the following usage restriction methods:

[0214] Before the network side device provides an available HARQ-ACK feedback time for the target HARQ process, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission;

[0215] Before the network side device provides available HARQ-ACK feedback time for the target HARQ process, when the first condition is not met, the terminal does not expect the target HARQ process to be scheduled or configured with new shared channel transmission.

[0216] Optionally, the first condition is: the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset;

[0217] The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

[0218] Optionally, the shared channel includes at least one of the following:

[0219] Physical downlink shared channel PDSCH;

[0220] Physical uplink shared channel PUSCH.

[0221] It should be noted that by including scheduling information for at least one shared channel in the first DCI for scheduling the transmission of at least one shared channel, at least one of the codeword indication information of multiple shared channels, VRB to PRB mapping information, PRB bundling size indication information, rate matching indication information, ZP CSI-RS trigger information and non-numerical feedback time offset is limited, so as to ensure that the actual application of scheduling of multiple shared channels is not affected.

[0222] The shared channel scheduling device in the embodiment of the present application can be a device, a device or electronic device with an operating system, or a component, an integrated circuit, or a chip in a terminal. The device or electronic device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0223] The shared channel scheduling device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0224] The embodiment of the present application further provides a terminal, including a processor and a communication interface, the communication interface is used to receive first downlink control information DCI, the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0225] The scheduling information includes at least one of the following:

[0226] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0227] This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 4 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0228] The terminal 400 includes but is not limited to: a radio frequency unit 401, a network module 402, an audio output unit 403, an input unit 404, a sensor 405, a display unit 406, a user input unit 407, an interface unit 408, a memory 409, and at least some of the components of a processor 410.

[0229] Those skilled in the art will appreciate that the terminal 400 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 410 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 4 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0230] It should be understood that in the embodiment of the present application, the input unit 404 may include a graphics processor (Graphics Processing Unit, GPU) 4041 and a microphone 4042, and the graphics processor 4041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 406 may include a display panel 4061, and the display panel 4061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 407 includes a touch panel 4071 and other input devices 4072. The touch panel 4071 is also called a touch screen. The touch panel 4071 may include two parts: a touch detection device and a touch controller. Other input devices 4072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0231] In the embodiment of the present application, the radio frequency unit 401 receives downlink data from the network side device and sends it to the processor 410 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 401 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0232] The memory 409 can be used to store software programs or instructions and various data. The memory 409 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 409 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0233] The processor 410 may include one or more processing units; optionally, the processor 410 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 410.

[0234] The radio frequency unit 401 is used to implement:

[0235] receiving first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0236] The scheduling information includes at least one of the following:

[0237] The at least one shared channel includes time domain resource allocation information, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0238] The terminal of the embodiment of the present application includes scheduling information for at least one shared channel in the first DCI for scheduling the transmission of at least one shared channel, so as to limit at least one of the codeword indication information of multiple shared channels, the mapping information of VRB to PRB, the PRB bundling size indication information, the rate matching indication information, the ZP CSI-RS trigger information and the non-numerical feedback time offset, so as to ensure that the actual application of the scheduling of multiple shared channels is not affected.

[0239] Optionally, before the radio frequency unit 401 receives the first downlink control information DCI, the radio frequency unit 401 is further configured to:

[0240] Receive configuration information of a time domain resource allocation table from a network side device;

[0241] The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following:

[0242] Each time domain resource allocation record in the target row corresponds to a transmission time offset;

[0243] Each time domain resource allocation record subset in the target row corresponds to a transmission time offset;

[0244] The target row is any row in the time domain resource allocation table.

[0245] Optionally, when dual codeword transmission is allowed, the indication of the codeword indication information satisfies any one of the following:

[0246] Use an independent indication field to indicate the enable status of each codeword;

[0247] The first value combination of the first indication field is used to indicate the enabling state of each codeword.

[0248] Optionally, when an independent indication field is used to indicate the enable state of each codeword, the indication of the codeword indication information satisfies one of the following:

[0249] The independent indication field is used to indicate the enabling state of each codeword of at least one shared channel scheduled by the first DCI;

[0250] The independent indication field respectively indicates the enabling status of each codeword of each shared channel scheduled by the first DCI.

[0251] Optionally, when the first value combination of the first indication field is used to indicate the enable state of each codeword, the enable state of each codeword is determined using one of the following rules:

[0252] When each transport block TB of each shared channel scheduled by the first DCI corresponds to two redundant version RV indication bits, if the first modulation and coding strategy MCS index corresponding to the first target TB is a preset MCS index and the first RV index corresponding to the first target TB is a preset RV index, it is determined that the first target TB is in a disabled state;

[0253] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is a preset MCS index and the second RV index corresponding to the second target TB is one of the two RV index values ​​corresponding to the one RV indication bit, it is determined that the second target TB is in a disabled state;

[0254] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the third MCS index corresponding to the third target TB is a preset MCS index and the third RV index corresponding to the third target TB is one of the two RV index values ​​corresponding to the one RV indication bit, and the value of the second indication field corresponding to the third target TB meets a preset condition, it is determined that the third target TB is in a disabled state;

[0255] Among them, the first target TB, the second target TB, and the third target TB are any TBs corresponding to any shared channel scheduled by the first DCI.

[0256] Optionally, the second indication field includes a new data indication NDI indication field corresponding to the third target TB, and the preset condition includes one of the following:

[0257] The NDI indication field is a preset value;

[0258] The value of the NDI indication field is flipped or not flipped relative to the NDI value before the first HARQ process, and the first HARQ process is the HARQ process occupied by the shared channel corresponding to the third target TB.

[0259] Optionally, when the terminal supports resource allocation type 1 and supports interleaving-based VRB-to-PRB mapping, the indication of the VRB-to-PRB mapping information includes one of the following:

[0260] The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel;

[0261] The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set;

[0262] The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

[0263] Optionally, when dynamic PRB bundling is adopted, the indication of the PRB bundling size indication information includes one of the following:

[0264] The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel;

[0265] The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set;

[0266] The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

[0267] Optionally, in the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the indication of the rate matching indication information includes one of the following:

[0268] The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel;

[0269] The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set;

[0270] The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

[0271] Optionally, in the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the indication of the ZP CSI-RS triggering information includes one of the following:

[0272] The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following:

[0273] a target shared channel in a set of scheduled shared channels;

[0274] a target time unit among the time units occupied by the scheduled shared channel set;

[0275] Each shared channel scheduled;

[0276] Each time unit in the time units occupied by the scheduled shared channel set.

[0277] Optionally, the target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

[0278] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0279] Optionally, in a case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process for which an available hybrid automatic repeat request answer HARQ-ACK feedback time is not provided, the terminal complies with one of the following usage restriction methods:

[0280] Before the network side device provides an available HARQ-ACK feedback time for the target HARQ process, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission;

[0281] Before the network side device provides available HARQ-ACK feedback time for the target HARQ process, when the first condition is not met, the terminal does not expect the target HARQ process to be scheduled or configured with new shared channel transmission.

[0282] Optionally, the first condition is: the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset;

[0283] The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

[0284] Optionally, the shared channel includes at least one of the following:

[0285] Physical downlink shared channel PDSCH;

[0286] Physical uplink shared channel PUSCH.

[0287] Preferably, an embodiment of the present application also provides a terminal, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of an embodiment of the shared channel scheduling method is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0288] The embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the embodiment of the shared channel scheduling method is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. Among them, the computer-readable storage medium is such as a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0289] like Figure 5 As shown, the embodiment of the present application also provides a shared channel scheduling method, including:

[0290] Step 501: A network-side device sends first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0291] The scheduling information includes at least one of the following:

[0292] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0293] Optionally, before the network side device sends the first downlink control information DCI, the method further includes:

[0294] The network side device sends the configuration information of the time domain resource allocation table to the terminal;

[0295] The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following:

[0296] Each time domain resource allocation record in the target row corresponds to a feedback transmission time offset;

[0297] Each time domain resource allocation record subset in the target row corresponds to a feedback transmission time offset;

[0298] The target row is any row in the time domain resource allocation table.

[0299] Optionally, when dual codeword transmission is allowed, the indication of the codeword indication information satisfies any one of the following:

[0300] Use an independent indication field to indicate the enable status of each codeword;

[0301] The first value combination of the first indication field is used to indicate the enabling state of each codeword.

[0302] Optionally, when an independent indication field is used to indicate the enable state of each codeword, the indication of the codeword indication information satisfies one of the following:

[0303] The independent indication field is used to indicate the enabling state of each codeword of at least one shared channel scheduled by the first DCI;

[0304] The independent indication field respectively indicates the enabling status of each codeword of each shared channel scheduled by the first DCI.

[0305] Optionally, when the first value combination of the first indication field is used to indicate the enable state of each codeword, the enable state of each codeword is determined using one of the following rules:

[0306] When each transport block TB of each shared channel scheduled by the first DCI corresponds to two redundant version RV indication bits, if the first modulation and coding strategy MCS index corresponding to the first target TB is a preset MCS index and the first RV index corresponding to the first target TB is a preset RV index, it is determined that the first target TB is in a disabled state;

[0307] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is a preset MCS index and the second RV index corresponding to the second target TB is one of the two RV index values ​​corresponding to the one RV indication bit, it is determined that the second target TB is in a disabled state;

[0308] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the third MCS index corresponding to the third target TB is a preset MCS index and the third RV index corresponding to the third target TB is one of the two RV index values ​​corresponding to the one RV indication bit, and the value of the second indication field corresponding to the third target TB meets a preset condition, it is determined that the third target TB is in a disabled state;

[0309] Among them, the first target TB, the second target TB, and the third target TB are any TBs corresponding to any shared channel scheduled by the first DCI.

[0310] Optionally, the second indication field includes a new data indication NDI indication field corresponding to the third target TB, and the preset condition includes one of the following:

[0311] The NDI indication field is a preset value;

[0312] The value of the NDI indication field is flipped or not flipped relative to the NDI value before the first HARQ process, and the first HARQ process is the HARQ process occupied by the shared channel corresponding to the third target TB.

[0313] Optionally, when the terminal supports resource allocation type 1 and supports interleaving-based VRB-to-PRB mapping, the indication of the VRB-to-PRB mapping information includes one of the following:

[0314] The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel;

[0315] The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set;

[0316] The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

[0317] Optionally, when dynamic PRB bundling is adopted, the indication of the PRB bundling size indication information includes one of the following:

[0318] The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel;

[0319] The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set;

[0320] The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

[0321] Optionally, in the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the indication of the rate matching indication information includes one of the following:

[0322] The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel;

[0323] The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set;

[0324] The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

[0325] Optionally, in the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the indication of the ZP CSI-RS triggering information includes one of the following:

[0326] The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following:

[0327] a target shared channel in a set of scheduled shared channels;

[0328] a target time unit among the time units occupied by the scheduled shared channel set;

[0329] Each shared channel scheduled;

[0330] Each time unit in the time units occupied by the scheduled shared channel set.

[0331] Optionally, the target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

[0332] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0333] Optionally, in a case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process that does not provide an available hybrid automatic repeat request answer HARQ-ACK feedback time, the network side device follows one of the following usage restriction methods:

[0334] Before the available HARQ-ACK feedback time is provided for the target HARQ process, the target HARQ process cannot be scheduled or configured for new shared channel transmission;

[0335] Before available HARQ-ACK feedback time is provided for the target HARQ process, when a first condition is met, the target HARQ process is allowed to be scheduled or configured with a new shared channel transmission.

[0336] Optionally, the first condition is: the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset;

[0337] The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

[0338] Optionally, the shared channel includes at least one of the following:

[0339] Physical downlink shared channel PDSCH;

[0340] Physical uplink shared channel PUSCH.

[0341] It should be noted that all descriptions about the network-side device in the above embodiments are applicable to the embodiments of the shared channel scheduling method applied to the network-side device, and can achieve the same technical effects.

[0342] It should be noted that, in an embodiment of the present application, the first DCI for scheduling the transmission of at least one shared channel includes scheduling information for the at least one shared channel, which is used to limit at least one of the codeword indication information of multiple shared channels, the mapping information of VRB to PRB, the PRB binding size indication information, the rate matching indication information, the ZP CSI-RS trigger information and the non-numerical feedback time offset, so as to ensure that the actual application of the scheduling of multiple shared channels is not affected.

[0343] like Figure 6 As shown, the embodiment of the present application further provides a shared channel scheduling device 600, including:

[0344] A sending module 601 is configured to send first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0345] The scheduling information includes at least one of the following:

[0346] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0347] Optionally, before the network side device sends the first downlink control information DCI, the method further includes:

[0348] A configuration sending module is used to send configuration information of the time domain resource allocation table to the terminal;

[0349] The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following:

[0350] Each time domain resource allocation record in the target row corresponds to a feedback transmission time offset;

[0351] Each time domain resource allocation record subset in the target row corresponds to a feedback transmission time offset;

[0352] The target row is any row in the time domain resource allocation table.

[0353] Optionally, when dual codeword transmission is allowed, the indication of the codeword indication information satisfies any one of the following:

[0354] Use an independent indication field to indicate the enable status of each codeword;

[0355] The first value combination of the first indication field is used to indicate the enabling state of each codeword.

[0356] Optionally, when an independent indication field is used to indicate the enable state of each codeword, the indication of the codeword indication information satisfies one of the following:

[0357] The independent indication field is used to indicate the enabling state of each codeword of at least one shared channel scheduled by the first DCI;

[0358] The independent indication field respectively indicates the enabling status of each codeword of each shared channel scheduled by the first DCI.

[0359] Optionally, when the first value combination of the first indication field is used to indicate the enable state of each codeword, the enable state of each codeword is determined using one of the following rules:

[0360] When each transport block TB of each shared channel scheduled by the first DCI corresponds to two redundant version RV indication bits, if the first modulation and coding strategy MCS index corresponding to the first target TB is a preset MCS index and the first RV index corresponding to the first target TB is a preset RV index, it is determined that the first target TB is in a disabled state;

[0361] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is a preset MCS index and the second RV index corresponding to the second target TB is one of the two RV index values ​​corresponding to the one RV indication bit, it is determined that the second target TB is in a disabled state;

[0362] When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the third MCS index corresponding to the third target TB is a preset MCS index and the third RV index corresponding to the third target TB is one of the two RV index values ​​corresponding to the one RV indication bit, and the value of the second indication field corresponding to the third target TB meets a preset condition, it is determined that the third target TB is in a disabled state;

[0363] Among them, the first target TB, the second target TB, and the third target TB are any TBs corresponding to any shared channel scheduled by the first DCI.

[0364] Optionally, the second indication field includes a new data indication NDI indication field corresponding to the third target TB, and the preset condition includes one of the following:

[0365] The NDI indication field is a preset value;

[0366] The value of the NDI indication field is flipped or not flipped relative to the NDI value before the first HARQ process, and the first HARQ process is the HARQ process occupied by the shared channel corresponding to the third target TB.

[0367] Optionally, when the terminal supports resource allocation type 1 and supports interleaving-based VRB-to-PRB mapping, the indication of the VRB-to-PRB mapping information includes one of the following:

[0368] The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel;

[0369] The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set;

[0370] The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

[0371] Optionally, when dynamic PRB bundling is adopted, the indication of the PRB bundling size indication information includes one of the following:

[0372] The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel;

[0373] The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set;

[0374] The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

[0375] Optionally, in the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the indication of the rate matching indication information includes one of the following:

[0376] The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel;

[0377] The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set;

[0378] The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

[0379] Optionally, in the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the indication of the ZP CSI-RS triggering information includes one of the following:

[0380] The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following:

[0381] a target shared channel in a set of scheduled shared channels;

[0382] a target time unit among the time units occupied by the scheduled shared channel set;

[0383] Each shared channel scheduled;

[0384] Each time unit in the time units occupied by the scheduled shared channel set.

[0385] Optionally, the target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

[0386] Optionally, the target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

[0387] Optionally, in a case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process that does not provide an available hybrid automatic repeat request answer HARQ-ACK feedback time, the network side device follows one of the following usage restriction methods:

[0388] Before the available HARQ-ACK feedback time is provided for the target HARQ process, the target HARQ process cannot be scheduled or configured for new shared channel transmission;

[0389] Before available HARQ-ACK feedback time is provided for the target HARQ process, when a first condition is met, the target HARQ process is allowed to be scheduled or configured with a new shared channel transmission.

[0390] Optionally, the first condition is: the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset;

[0391] The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

[0392] Optionally, the shared channel includes at least one of the following:

[0393] Physical downlink shared channel PDSCH;

[0394] Physical uplink shared channel PUSCH.

[0395] It should be noted that the device embodiment is a device that corresponds one-to-one to the above-mentioned method embodiment, and all implementation methods in the above-mentioned method embodiment are applicable to the device embodiment and can achieve the same technical effect.

[0396] Preferably, an embodiment of the present application also provides a network side device, including a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, the various processes of the shared channel scheduling method embodiment applied to the network side device side are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0397] An embodiment of the present application also provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the shared channel scheduling method embodiment applied to the network side device side are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0398] The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0399] The embodiment of the present application further provides a network side device, including a processor and a communication interface, the communication interface is used to send first downlink control information DCI, the first DCI is used to schedule the transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel;

[0400] The scheduling information includes at least one of the following:

[0401] The time domain resource allocation information corresponding to the at least one shared channel includes the index of the shared channel scheduled by the first DCI in the time domain resource allocation table, codeword indication information, mapping information of virtual resource blocks VRB to physical resource blocks PRB, PRB bundling size indication information, rate matching indication information, zero power channel state information reference signal ZP CSI-RS trigger information and non-numerical feedback time offset.

[0402] This network side device embodiment corresponds to the above-mentioned network side device method embodiment. Each implementation process and implementation method of the above-mentioned method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.

[0403] Specifically, the embodiment of the present application also provides a network side device. Figure 7 As shown, the network side device 700 includes: an antenna 71, a radio frequency device 72, and a baseband device 73. The antenna 71 is connected to the radio frequency device 72. In the uplink direction, the radio frequency device 72 receives information through the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be sent and sends it to the radio frequency device 72. The radio frequency device 72 processes the received information and sends it out through the antenna 71.

[0404] The frequency band processing device may be located in a baseband device 73 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 73 . The baseband device 73 includes a processor 74 and a memory 75 .

[0405] The baseband device 73 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 7 As shown, one of the chips is, for example, a processor 74, which is connected to a memory 75 to call a program in the memory 75 to execute the network-side device operations shown in the above method embodiment.

[0406] The baseband device 73 may further include a network interface 76 for exchanging information with the radio frequency device 72 , and the interface may be, for example, a common public radio interface (CPRI for short).

[0407] Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 75 and executable on the processor 74, and the processor 74 calls the instructions or programs in the memory 75 to execute Figure 6 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0408] Optional, such as Figure 8 As shown, the embodiment of the present application also provides a communication device 800, including a processor 801, a memory 802, and a program or instruction stored in the memory 802 and executable on the processor 801. For example, when the communication device 800 is a terminal, the program or instruction is executed by the processor 801 to implement the various processes of the above-mentioned shared channel scheduling method embodiment applied to the terminal, and can achieve the same technical effect. When the communication device 800 is a network side device, the program or instruction is executed by the processor 801 to implement the various processes of the above-mentioned shared channel scheduling method embodiment applied to the network side device, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0409] The terminal involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.

[0410] The network side device involved in the embodiments of the present application can be a base station (Base Transceiver Station, BTS) in Global System of Mobile communication (GSM) or Code Division Multiple Access (CDMA), or a base station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a base station in the future 5G network, etc., which is not limited here.

[0411] The network side device and the terminal can each use one or more antennas for multi-input multi-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.

[0412] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned shared channel scheduling method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0413] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0414] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be noted that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0415] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0416] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A shared channel scheduling method, characterized in that: include: The terminal receives first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel; The scheduling information includes: Codeword indication information, wherein the codeword indication information indicates an enabling state of each codeword by using a first value combination of a first indication field; In the case where dual codeword transmission is allowed, the codeword indication information indicates the enabling state of each codeword by using a first value combination of the first indication field, including: When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is 26 and the second RV index corresponding to the second target TB is 2, it is determined that the second target TB is in a disabled state; The second target TB is any TB corresponding to any shared channel scheduled by the first DCI.

2. The method according to claim 1, characterized in that The scheduling information further includes time domain resource allocation information corresponding to the at least one shared channel, and before the terminal receives the first downlink control information DCI, further includes: Receive configuration information of a time domain resource allocation table from a network side device; The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following: Each time domain resource allocation record in the target row corresponds to a transmission time offset; Each time domain resource allocation record subset in the target row corresponds to a transmission time offset; The target row is any row in the time domain resource allocation table.

3. The method according to claim 1, characterized in that When the terminal supports resource allocation type 1 and supports interleaving-based VRB to PRB mapping, the scheduling information further includes mapping information of virtual resource blocks VRB to physical resource blocks PRB, and the indication of the mapping information of VRB to PRB includes one of the following: The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

4. The method according to claim 1, characterized in that: In the case of adopting dynamic PRB bundling, the scheduling information further includes PRB bundling size indication information, and the indication of the PRB bundling size indication information includes one of the following: The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

5. The method according to claim 1, characterized in that In the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the scheduling information further includes rate matching indication information, and the indication of the rate matching indication information includes one of the following: The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

6. The method according to claim 1, characterized in that In the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the scheduling information further includes zero-power channel state information reference signal ZP CSI-RS triggering information, and the indication of the ZP CSI-RS triggering information includes one of the following: The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following: a target shared channel in a set of scheduled shared channels; a target time unit among the time units occupied by the scheduled shared channel set; Each shared channel scheduled; Each time unit in the time units occupied by the scheduled shared channel set.

7. The method according to claim 6, characterized in that The target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

8. The method according to any one of claims 3 to 6, characterized in that: The target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

9. The method according to claim 1, characterized in that: In the case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process that does not provide an available hybrid automatic repeat request answer HARQ-ACK feedback time, the terminal complies with one of the following usage restriction modes: Before the network side device provides an available HARQ-ACK feedback time for the target HARQ process, the terminal does not expect the target HARQ process to be scheduled or configured with a new shared channel transmission; Before the network side device provides available HARQ-ACK feedback time for the target HARQ process, when the first condition is not met, the terminal does not expect the target HARQ process to be scheduled or configured with new shared channel transmission.

10. The method according to claim 9, characterized in that The first condition is that the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset; The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

11. The method according to claim 1, characterized in that: The shared channel includes at least one of the following: Physical downlink shared channel PDSCH; Physical uplink shared channel PUSCH.

12. A shared channel scheduling method, characterized in that: include: The network side device sends first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel; The scheduling information includes: Codeword indication information, wherein the codeword indication information indicates an enabling state of each codeword by using a first value combination of a first indication field; In the case where dual codeword transmission is allowed, the codeword indication information indicates the enabling state of each codeword by using a first value combination of the first indication field, including: When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is 26 and the second RV index corresponding to the second target TB is 2, it is determined that the second target TB is in a disabled state; The second target TB is any TB corresponding to any shared channel scheduled by the first DCI.

13. The method according to claim 12, characterized in that Before the network side device sends the first downlink control information DCI, the method further includes: The network side device sends the configuration information of the time domain resource allocation table to the terminal; The configuration information is used to configure a target row in the time domain resource allocation table, and the configuration rule of the target row includes any one of the following: Each time domain resource allocation record in the target row corresponds to a feedback transmission time offset; Each time domain resource allocation record subset in the target row corresponds to a feedback transmission time offset; The target row is any row in the time domain resource allocation table.

14. The method according to claim 12, characterized in that When the terminal supports resource allocation type 1 and supports interleaving-based VRB to PRB mapping, the scheduling information further includes mapping information of virtual resource blocks VRB to physical resource blocks PRB, and the indication of the mapping information of VRB to PRB includes one of the following: The first DCI includes multiple indication fields, each indication field indicates the mapping information of the VRB to the PRB corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the mapping information of the VRB to the PRB corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the VRB-to-PRB mapping information indicated by the indication field is applied to each scheduled shared channel.

15. The method according to claim 12, characterized in that In the case of adopting dynamic PRB bundling, the scheduling information further includes PRB bundling size indication information, and the indication of the PRB bundling size indication information includes one of the following: The first DCI includes multiple indication fields, each indication field indicating the PRB bundling size corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the PRB bundling size corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the PRB bundling size indicated by the indication field is applied to each scheduled shared channel.

16. The method according to claim 12, characterized in that In the case where it is necessary to dynamically indicate whether a resource set corresponding to rate matching pattern group 1 and / or rate matching pattern group 2 can be used for shared channel transmission, the scheduling information further includes rate matching indication information, and the indication of the rate matching indication information includes one of the following: The first DCI includes multiple indication fields, each indication field indicates the rate matching indication information corresponding to a scheduled shared channel; The first DCI includes an indication field, where the indication field is used to indicate the rate matching indication information corresponding to the target shared channel in the scheduled shared channel set; The first DCI includes an indication field, and the rate matching indication information indicated by the indication field is applied to each scheduled shared channel.

17. The method according to claim 12, characterized in that In the case where a non-periodic ZP CSI-RS resource set needs to be dynamically indicated, the scheduling information further includes zero-power channel state information reference signal ZP CSI-RS triggering information, and the indication of the ZP CSI-RS triggering information includes one of the following: The first DCI includes an indication field, and the ZP CSI-RS triggering information indicated by the indication field is applied to one of the following: a target shared channel in a set of scheduled shared channels; a target time unit among the time units occupied by the scheduled shared channel set; Each shared channel scheduled; Each time unit in the time units occupied by the scheduled shared channel set.

18. The method according to claim 17, characterized in that The target time unit is the first time unit, the last time unit or the time unit with a preset index occupied by the shared channel set scheduled by the first DCI.

19. The method according to any one of claims 14 to 17, characterized in that: The target shared channel is the first shared channel, the last shared channel or a shared channel with a preset index scheduled by the first DCI.

20. The method according to claim 12, characterized in that In the case where the first DCI includes a non-numerical feedback time offset, for a target HARQ process that does not provide an available hybrid automatic repeat request acknowledgment HARQ-ACK feedback time, the network side device follows one of the following usage restriction methods: Before the available HARQ-ACK feedback time is provided for the target HARQ process, the target HARQ process cannot be scheduled or configured for new shared channel transmission; Before available HARQ-ACK feedback time is provided for the target HARQ process, when a first condition is met, the target HARQ process is allowed to be scheduled or configured with a new shared channel transmission.

21. The method according to claim 20, characterized in that The first condition is that the start time of the new shared channel transmission scheduled or configured by the target HARQ process is after the transmission end time of the first shared channel transmission, or after the end time of the first shared channel transmission is offset by a predefined time offset; The first shared channel transmission occupies the target HARQ process, and a non-numerical feedback time offset is indicated in the DCI that schedules the first shared channel transmission.

22. The method according to claim 12, characterized in that The shared channel includes at least one of the following: Physical downlink shared channel PDSCH; Physical uplink shared channel PUSCH.

23. A shared channel scheduling device, characterized in that: include: A receiving module, configured to receive first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel; The scheduling information includes: Codeword indication information, wherein the codeword indication information indicates an enabling state of each codeword by using a first value combination of a first indication field; In the case where dual codeword transmission is allowed, the codeword indication information indicates the enabling state of each codeword by using a first value combination of the first indication field, including: When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is 26 and the second RV index corresponding to the second target TB is 2, it is determined that the second target TB is in a disabled state; The second target TB is any TB corresponding to any shared channel scheduled by the first DCI.

24. A terminal, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the steps of the shared channel scheduling method as described in any one of claims 1 to 11 are implemented.

25. A shared channel scheduling device, characterized in that: include: A sending module, configured to send first downlink control information DCI, where the first DCI is used to schedule transmission of at least one shared channel, and the first DCI includes scheduling information for the at least one shared channel; The scheduling information includes: Codeword indication information, wherein the codeword indication information indicates an enabling state of each codeword by using a first value combination of a first indication field; In the case where dual codeword transmission is allowed, the codeword indication information indicates the enabling state of each codeword by using a first value combination of the first indication field, including: When each TB of each shared channel scheduled by the first DCI corresponds to an RV indication bit, if the second MCS index corresponding to the second target TB is 26 and the second RV index corresponding to the second target TB is 2, it is determined that the second target TB is in a disabled state; The second target TB is any TB corresponding to any shared channel scheduled by the first DCI.

26. A network side device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the shared channel scheduling method as described in any one of claims 12 to 22.

27. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the shared channel scheduling method as described in any one of claims 1-22 are implemented.

Images