PDCCH Verification Method, Transmission Method, Terminal, and Network Side Device

Abstract

The present application discloses a verification method, a transmission method, a terminal and a network-side device for PDCCH, belonging to the field of wireless communication technologies. The verification method for PDCCH applied to a terminal includes: receiving a first DCI; if the target bit position in the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission, the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of an NDI field and an RVI field. The present application clarifies the verification and configuration method for DCI scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission, so that the terminal can accurately determine the timing for activation or deactivation of semi-static transmission.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technologies, and particularly relates to a method for verifying a Physical Downlink Control Channel (PDCCH), a method for transmitting the same, a terminal, and a network-side device. Background Art

[0002] In New Radio Unlicensed spectrum (NRU) in Release 16, scheduling of multiple Physical Uplink Shared Channels (Multi-PUSCH) is introduced for Downlink Control Information (DCI) format 0_1. However, in related technologies, when designing the activation or deactivation of semi-static transmission using DCI, only the DCI for scheduling a single PUSCH (Single-PUSCH) is considered for the activation or deactivation of semi-static transmission. How to use the DCI for scheduling Multi-PUSCH for the activation or deactivation of semi-static transmission is a problem to be solved. Summary of the Invention

[0003] The purpose of the embodiments of this application is to provide a method for verifying a PDCCH, a method for transmitting the same, a terminal, and a network-side device, so as to solve the problem of how to use the DCI for scheduling Multi-PUSCH for the activation or deactivation of semi-static transmission.

[0004] To solve the above technical problem, this application is implemented as follows:

[0005] In a first aspect, a method for verifying a PDCCH is provided, which is applied to a terminal. The method includes:

[0006] Receiving a first Downlink Control Information (DCI);

[0007] If the target bit position in the first indication field of the first DCI indicates '0' or not all '1's or a preset value, determining that the first DCI is used for the activation or deactivation of semi-static transmission. The first indication field corresponds to multiple Physical Uplink Shared Channels (PUSCH), and the first indication field includes at least one of a New Data Indicator (NDI) field and a Redundancy Version Indicator (RVI) field.

[0008] In a second aspect, a device for verifying a PDCCH is provided, including:

[0009] A first receiving module, configured to receive a first DCI;

[0010] The first verification module is used to determine that the first DCI is used for activation or deactivation of semi-static transmission if the target bit position in the first indication field of the first DCI indicates '0' or not all '1' or a preset value. The first indication field corresponds to multiple physical uplink shared channels (PUSCHs), and the first indication field includes at least one of the NDI field and the RVI field.

[0011] Optionally, the first verification module is used to determine that the first DCI is used for activation or deactivation of semi-static transmission if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the target bit position in the first indication field of the first DCI indicates '0' or not all '1' or a preset value.

[0012] Optionally, the target bit position is one of the following:

[0013] All bit positions;

[0014] The bit positions corresponding to the valid PUSCH;

[0015] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0016] Optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

[0017] Optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

[0018] Optionally, the target bit position indicating not all '1' includes that one position in the target bit positions is '0' and the rest are '1'.

[0019] Optionally, if all bit positions in the first indication field indicate '0' or not all '1' or a preset value, or all bit positions corresponding to the valid PUSCH in the first indication field indicate '0', the verification device of the PDCCH further includes:

[0020] The first determination module is used to determine that the starting and length indication value SLIV used for the activated semi-static transmission is a predefined SLIV among the valid SLIVs in the time domain resource allocation TDRA field of the first DCI.

[0021] Optionally, if the first N bit positions or the last N bit positions of the first indication field indicate '0', the verification device of the PDCCH further includes:

[0022] The second determination module is used to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions of the TDRA field of the first DCI.

[0023] Optionally, if the bit positions corresponding to the valid PUSCH of the first indication field indicate non-all '1', the verification device of the PDCCH further includes:

[0024] The third determination module is used to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, where the target valid PUSCH is the valid PUSCH corresponding to the position indicating '0' among the bit positions corresponding to the valid PUSCH in the first indication field.

[0025] Optionally, the verification device of the PDCCH further includes:

[0026] The second verification module is used to determine that the first DCI is used for deactivation of semi-static transmission if the first DCI further satisfies at least one of the following conditions:

[0027] The HARQ process number field of the first DCI indicates all '0';

[0028] The modulation and coding scheme MCS field of the first DCI indicates all '0';

[0029] The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

[0030] Optionally, the verification device of the PDCCH further includes:

[0031] The second receiving module is used to receive the second DCI;

[0032] A third verification module, configured to determine that the second DCI is used for scheduling retransmission of semi-static transmission if the PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and all valid PUSCH position indications in the NDI field of the second DCI are '1'.

[0033] Optionally, the semi-static transmission is an SPS PDSCH transmission, a second type of configured grant PUSCH transmission, or a semi-static CSI transmission.

[0034] In a third aspect, a method for transmitting a PDCCH is provided, which is applied to a network-side device and includes:

[0035] Transmitting a first DCI for activating or deactivating semi-static transmission, where a target bit position of a first indication field of the first DCI indicates '0' or is not all '1' or a preset value, and the first indication field includes at least one of an NDI field and an RVI field.

[0036] In a fourth aspect, a transmission device for a PDCCH is provided, including:

[0037] A first transmission module, configured to transmit a first DCI for activating or deactivating semi-static transmission, where a target bit position of a first indication field of the first DCI indicates '0' or is not all '1' or a preset value, and the first indication field includes at least one of an NDI field and an RVI field.

[0038] Optionally, the PDCCH transmitting the first DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.

[0039] Optionally, the target bit position is one of the following:

[0040] All bit positions;

[0041] Bit positions corresponding to valid PUSCH;

[0042] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0043] Optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCH scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

[0044] Optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

[0045] Optionally, the indication that the target bit position is not all '1' means that one position in the target bit position is '0' and the rest are '1'.

[0046] Optionally, if the first DCI is used for deactivation of semi-static transmission, the first DCI further satisfies at least one of the following conditions:

[0047] The HARQ process number field of the first DCI indicates all '0's;

[0048] The modulation and coding scheme MCS field of the first DCI indicates all '0's;

[0049] The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

[0050] Optionally, the transmission device of the PDCCH further includes:

[0051] A second transmission module, configured to transmit a second DCI for scheduling retransmission of semi-static transmission. The PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI. The DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the positions of the valid PUSCHs in the NDI field of the second DCI indicate all '1's.

[0052] Optionally, the semi-static transmission is SPS PDSCH transmission, or second-type configured grant PUSCH transmission, or semi-static CSI transmission.

[0053] In a fifth aspect, a terminal is provided. The terminal includes 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 steps of the method described in the first aspect are implemented.

[0054] In a sixth aspect, a network-side device is provided. The network-side device includes 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 steps of the method described in the third aspect are implemented.

[0055] In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, and when the program or instructions are executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the third aspect are implemented.

[0056] In an eighth aspect, a chip is provided, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a network-side device program or instructions to implement the method described in the first aspect or the method described in the third aspect.

[0057] In a ninth aspect, a program product is provided, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the method described in the first aspect or the method described in the third aspect.

[0058] In the embodiments of the present application, a method for verifying and configuring DCI for scheduling Multi-PUSCH for activation or deactivation of semi-static transmission is defined, so that the terminal can accurately determine the timing for activation or deactivation of semi-static transmission. Description of the Drawings

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

[0060] Figure 2 is a schematic flowchart of a method for checking a PDCCH in the embodiments of the present application;

[0061] Figure 3 is a schematic flowchart of a method for transmitting a PDCCH in the embodiments of the present application;

[0062] Figure 4 is a schematic structural diagram of a device for checking a PDCCH in the embodiments of the present application;

[0063] Figure 5 is a schematic structural diagram of a device for transmitting a PDCCH in the embodiments of the present application;

[0064] Figure 6 is a schematic structural diagram of a communication device in the embodiments of the present application;

[0065] Figure 7 is a schematic structural diagram of a terminal in the embodiments of the present application;

[0066] Figure 8 is a schematic structural diagram of a network-side device in the embodiments of the present application. Detailed Embodiments

[0067] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0068] The terms "first", "second", etc. in the description and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "and / or" in the description and claims means at least one of the connected objects, and the character " / " generally means that the associated objects before and after are in an "or" relationship.

[0069] It is worth pointing out 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, and 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 in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. However, the following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0070] Figure 1The block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device or a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. Terminal-side devices. Wearable devices include: bracelets, earphones, glasses, etc. It should be noted that in the embodiments of the present application, the specific type of the terminal 11 is not limited. The network-side device 12 can be a base station or a core network. Among them, the base station can be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an 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 Receiving Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments 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.

[0071] For the scenario of DCI scheduling a single PUSCH (Single-PUSCH), check whether the DCI is used to activate or deactivate semi-static transmission according to Table 1 and Table 2.

[0072] Table 1 Configuration of DCI for Activating Semi-Static Transmission

[0073]

[0074] Table 2 Configuration for Deactivating Semi-Static Transmission

[0075]

[0076] When the activation or deactivation of semi-static transmission in the related art is designed using DCI, only the activation or deactivation of semi-static transmission using DCI for scheduling a single PUSCH is considered. How to use DCI for scheduling Multi-PUSCH to activate or deactivate semi-static transmission is a problem to be solved.

[0077] The following will, in conjunction with the accompanying drawings, explain in detail the verification method, transmission method, terminal and network-side device of the PDCCH provided by the embodiments of the present application through specific embodiments and their application scenarios.

[0078] Please refer to Figure 2 , the embodiments of the present application provide a verification method for a Physical Downlink Control Channel (PDCCH), which is applied to a terminal and includes:

[0079] Step 21: Receive a first DCI;

[0080] The first DCI is DCI format 0_1 that supports scheduling Multi-PUSCH.

[0081] Step 22: If the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission. The first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of a New data indicator (NDI) and a Redundancy Version Indicator (RVI) field.

[0082] In the embodiments of the present application, the NDI field is the NDI of the enabled Transport Block (TB) in the DCI, and is used to indicate the time domain position of the scheduled PUSCH transmission.

[0083] In the embodiments of the present application, not all '1' means that the target bit position does not all indicate '1'. For example, one position in the target bit position is '0' and the rest are '1'.

[0084] In the embodiments of the present application, the preset value refers to a value different from all '0' and not all '1', such as '10', etc. The preset value can be agreed upon by the protocol.

[0085] In the embodiments of the present application, optionally, if the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission includes:

[0086] If the PDCCH transmitting the first DCI is scrambled by a Configured Scheduling Radio Network Temporary Identity (CS-RNTI) or a Semi-Persistent Scheduling Channel State Information Radio Network Temporary Identity (SP-CSI-RNTI), the Deep Flow Inspection (DFI) flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the target bit position of the first indication field of the first DCI indicates '0' or not all '1's or a preset value, it is determined that the first DCI is used for activation or deactivation of semi-static transmission.

[0087] In an embodiment of the present application, when it is detected that the PDCCH is scrambled by a CS-RNTI or an SP-CSI-RNTI, it can be considered that the first DCI in the PDCCH is used for retransmission of a Semi-Persistent Scheduling (SPS) Physical Downlink Shared Channel (PDSCH) or a Configured grant PUSCH, or for activation of an SPS PDSCH or a Type 2 Configured grant PUSCH or semi-static CSI transmission, or for deactivation of an SPS PDSCH or a Type 2 Configured grant PUSCH or semi-static CSI transmission, or for transmission of DFI.

[0088] Furthermore, when it is detected that the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, it can be considered that the first DCI is not used for DFI transmission. When it is detected that the target bit position of the first indication field indicates '0' or not all '1's or a preset value, it can be considered that the first DCI is used for activation or deactivation of semi-static transmission.

[0089] Optionally, the semi-static transmission is an SPS PDSCH transmission or a Type 2 Configured grant PUSCH transmission or a semi-static CSI transmission.

[0090] In an embodiment of the present application, a verification and configuration method for a DCI scheduling a Multi-PUSCH for activation or deactivation of semi-static transmission is clarified, so that a terminal can accurately determine the timing for activation or deactivation of semi-static transmission.

[0091] The following gives an example to illustrate the target bit position of the first indication field of the first DCI in the above embodiment.

[0092] In some embodiments of the present application, optionally, the target bit positions of the first indication field are all the bit positions of the first indication field. That is, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI is indicated as '0' or the DFI flag field does not exist, and all the bit positions of the first indication field indicate '0' or not all '1' or a preset value, it is determined that the first DCI is used for activation or deactivation of semi-static transmission. All bit positions indicating '0' can also be described as indicating all '0'.

[0093] In an embodiment of the present application, after determining that the first DCI is used for activation or deactivation of semi-static transmission if all the bit positions of the first indication field indicate '0' or not all '1' or a preset value, it further includes: determining that the start and length indicator value (SLIV) used for the activated semi-static transmission is a predefined SLIV among the valid SLIVs in the time domain resource allocation (TDRA) field of the first DCI.

[0094] In an embodiment of the present application, if a Multi-PUSCH TDRA table is configured, the terminal can determine the sizes of the respective fields in the first DCI according to the Multi-PUSCH TDRA table. Assuming that the maximum number of PUSCHs schedulable by the Multi-PUSCH TDRA table is M, the size of the NDI field in the first DCI is M*a bits, where a is the size of each PUSCH NDI in the NDI field, and the size of the RVI field in the first DCI is M*b bits, where b is the size of each PUSCH RVI in the RVI field.

[0095] The terminal can determine the Multi-PUSCH TDRA table according to Table 3.

[0096] Table 3

[0097]

[0098] It can be seen from Table 3 that:

[0099] 1) If the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-Config, the PUSCH time domain resource allocation table for DCI format 0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1) is not configured in pusch-Config, and the PUSCH time domain resource allocation table for multi-PUSCH (pusch-TimeDomainAllocationList–ForMultiPUSCH) is not configured in pusch-Config, then determine the Default A table as the Multi-PUSCH TDRA table.

[0100] 2) If the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is not configured in pusch-Config, the PUSCH time domain resource allocation table for DCI format 0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1) is not configured in pusch-Config, and the PUSCH time domain resource allocation table for multi-PUSCH (pusch-TimeDomainAllocationList–ForMultiPUSCH) is not configured in pusch-Config, then determine the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) configured in pusch-ConfigCommon as the Multi-PUSCH TDRA table.

[0101] 3) If the PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, the PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList) is configured in pusch-Config, the PUSCH time-domain resource allocation table for DCI format0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1) is not configured in pusch-Config, and the multi-PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList–ForMultiPUSCH) is not configured in pusch-Config, then determine the PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList) configured in pusch-Config as the Multi-PUSCH TDRA table.

[0102] 4) If the PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, the PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-Config, the PUSCH time-domain resource allocation table for DCI format0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1) is configured in pusch-Config, and the multi-PUSCH time-domain resource allocation table (pusch-TimeDomainAllocationList–ForMultiPUSCH) does not exist in pusch-Config, then determine the PUSCH time-domain resource allocation table for DCI format0_1 (pusch-TimeDomainAllocationList-ForDCIformat0_1) configured in pusch-Config as the Multi-PUSCH TDRA table.

[0103] 5) If the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-ConfigCommon, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList) is configured or not configured in pusch-Config, the PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList-ForDCIformat0_1) for DCI format0_1 does not exist in pusch-Config, and the Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList–ForMultiPUSCH) is configured in pusch-Config, then determine the Multi PUSCH time domain resource allocation table (pusch-TimeDomainAllocationList–ForMultiPUSCH) configured in pusch-Config as the Multi-PUSCH TDRA table.

[0104] Assume that the number of valid PUSCHs actually scheduled in the TDRA field of the first DCI is M' (1 <= M' <= M)), and each PUSCH corresponds to an SLIV. For example, the SLIVs corresponding to the M' PUSCHs can be SLIV0, SLIV1,..., SLIV M’-1 The valid SLIV refers to the SLIV corresponding to the actually scheduled valid PUSCH, for example, SLIV0.

[0105] In some embodiments of the present application, optionally, the target bit position of the first indication field is the bit position corresponding to the valid PUSCH of the first indication field. That is, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the bit position corresponding to the valid PUSCH of the first indication field indicates '0' or not all '1' or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission. The bit position corresponding to the valid PUSCH indicating '0' can also be described as the position of the valid PUSCH indicating all '0'.

[0106] In the embodiments of the present application, optionally, the bit position corresponding to the valid PUSCH in the NDI field of the first DCI is determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.

[0107] In an embodiment of the present application, optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field. That is to say, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI indicating '0' or not all '1' or a preset value mean that the highest or lowest M'*a bits in the NDI field indicate '0' or not all '1' or a preset value.

[0108] In an embodiment of the present application, optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.

[0109] In an embodiment of the present application, optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field. That is to say, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI indicating '0' or not all '1' or a preset value mean that the highest or lowest M'*b bits in the RVI field indicate '0' or not all '1' or a preset value.

[0110] In an embodiment of the present application, optionally, after determining that the first DCI is used for activation or deactivation of semi-static transmission if the bit positions corresponding to the valid PUSCH in the first indication field indicate '0', it further includes: determining that the SLIV used for the activated semi-static transmission is a predefined SLIV among the valid SLIVs in the time domain resource allocation TDRA field of the first DCI.

[0111] In an embodiment of the present application, optionally, after determining that the first DCI is used for activation or deactivation of semi-static transmission if the bit positions corresponding to the valid PUSCH in the first indication field indicate not all '1', it further includes: determining that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, where the target valid PUSCH is the valid PUSCH corresponding to the position indicating '0' among the bit positions corresponding to the valid PUSCH in the first indication field.

[0112] In some embodiments of the present application, optionally, the target bit positions of the first indication field are the first N bit positions or the last N bit positions of the first indication field. That is, if the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI is indicated as '0' or the DFI flag field does not exist, and the first N bit positions or the last N bit positions of the first indication field indicate '0' or not all '1' or a preset value, it is determined that the first DCI is used for activation or deactivation of semi-static transmission. The positive integer indicating '0' at the first N bit positions or the last N bit positions can also be described as the first N bit positions or the last N bit positions indicating all '0'.

[0113] In embodiments of the present application, optionally, the first N bit positions or the last N bit positions are, for example, the first position or the last position.

[0114] In embodiments of the present application, optionally, after determining that the first DCI is used for activation or deactivation of semi-static transmission when the first N bit positions or the last N bit positions of the first indication field indicate '0', it further includes: determining that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the PUSCH at the first N bit positions or the last N bit positions in the TDRA field of the first DCI (for example, SLIV0 or SLIV M’-1 ).

[0115] In embodiments of the present application, optionally, after determining that the first DCI is used for activation or deactivation of semi-static transmission, it further includes: if the first DCI further satisfies at least one of the following conditions, determining that the first DCI is used for deactivation of semi-static transmission:

[0116] The HARQ process number field of the first DCI indicates all '0';

[0117] The modulation and coding scheme (MCS) field of the first DCI indicates all '0';

[0118] The frequency domain resource allocation (FDRA) field of the first DCI indicates invalid resource allocation. The FDRA field is used to indicate the frequency domain resources of the scheduled PUSCH.

[0119] That is, if the above conditions are not satisfied, the first DCI is used for activation of semi-static transmission.

[0120] In embodiments of the present application, optionally, the verification method of the PDCCH further includes:

[0121] Receive a second DCI;

[0122] If the PDCCH transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the valid PUSCH position indication in the NDI field of the second DCI is all '1', determine that the second DCI is used for scheduling retransmission of semi-static transmission.

[0123] The above verification method of the PDCCH of the present application will be described below in conjunction with specific embodiments.

[0124] Embodiment 1 of the present invention:

[0125] When the Multi-PUSCH TDRA table is configured, the DCI format 0_1 scrambled by CS-RNTI refers to the Multi-PUSCH TDRA table. Assume that the maximum number of schedulable PUSCHs in the configured Multi-PUSCH TDRA table is 4. When the TDRA field of the DCI indicates scheduling more than 1 PUSCH, the NDI field in the DCI is 4 bits and the RVI field is also 4 bits.

[0126] At this time, if one of the following conditions is met, the UE considers that the PDCCH is a DCI for activating semi-static transmission:

[0127] 1. The NDI and RVI of the DCI are '0000';

[0128] 2. The number of valid PUSCHs indicated by the TDRA field in the DCI (assume it is 2), and the NDI and RVI are '00xx';

[0129] 3. The first bit in the NDI and RVI of the DCI is '0', that is, the NDI and RVI are '0xxx';

[0130] 4. The number of valid PUSCHs indicated by the TDRA field in the DCI (assume it is 2), and the NDI and RVI are '01xx' or '10xx'.

[0131] Among them, for '01xx', SLIV0 is used; for '10xx', SLIV1 is used.

[0132] The above x is 0 or 1, or a predefined value.

[0133] Embodiment 2 of the present invention:

[0134] When configuring the Multi-PUSCH TDRA table, the DCI format 0_1 scrambled by the SP-CSI-RNTI refers to the Multi-PUSCH TDRA table. Assume that the maximum number of schedulable PUSCHs in the configured Multi-PUSCH TDRA table is 4. When the TDRA field in the DCI indicates scheduling more than 1 PUSCH, the NDI field in the DCI is 4 bits and the RVI field is also 4 bits.

[0135] At this time, if one of the following conditions is met, the UE considers this PDCCH to be the DCI for activating semi-static transmission:

[0136] 1. The RVI of the DCI is '0000';

[0137] 2. The number of valid PUSCHs indicated by the TDRA field in the DCI (assume it is 2), and the RVI is '00xx';

[0138] 3. The first bit in the RVI of the DCI is '0', that is, the RVI is '0xxx';

[0139] 4. The number of valid PUSCHs indicated by the TDRA field in the DCI (assume it is 2), and the RVI is '01xx' or '10xx'.

[0140] Among them, for '01xx', SLIV0 is used; for '10xx', SLIV1 is used.

[0141] The above x is 0 or 1, or a predefined value.

[0142] Please refer to Figure 3 , this embodiment of the present application also provides a method for sending a PDCCH, which is applied to a network-side device and includes:

[0143] Step 31: Transmit a first DCI for activating or deactivating semi-static transmission, where the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, and the first indication field includes at least one of the NDI field and the RVI field.

[0144] In this embodiment of the present application, the verification and configuration methods of the DCI for scheduling Multi-PUSCH for activating or deactivating semi-static transmission are clarified, so that the terminal can accurately determine the timing for activating or deactivating semi-static transmission.

[0145] In this embodiment of the present application, optionally, the first DCI also meets the following conditions: the PDCCH for transmitting the first DCI is scrambled by the CS-RNTI or the SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.

[0146] In the embodiments of the present application, optionally, the target bit position is one of the following:

[0147] All bit positions;

[0148] Bit positions corresponding to valid PUSCH;

[0149] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0150] In the embodiments of the present application, optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.

[0151] In the embodiments of the present application, optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI and a is the size of each PUSCH NDI in the NDI field.

[0152] In the embodiments of the present application, optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.

[0153] In the embodiments of the present application, optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI and b is the size of each PUSCH RVI in the RVI field.

[0154] In the embodiments of the present application, optionally, the target bit position indicating non-all '1's means that one position in the target bit positions is '0' and the rest are '1's.

[0155] In the embodiments of the present application, optionally, if the first DCI is used for deactivation of semi-static transmission, the first DCI further satisfies at least one of the following conditions:

[0156] The HARQ process number field of the first DCI indicates all '0's;

[0157] The modulation and coding scheme MCS field of the first DCI indicates all '0's;

[0158] The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

[0159] In an embodiment of the present application, optionally, the method for transmitting the PDCCH further includes:

[0160] Transmit a second DCI for scheduling retransmission for semi-static transmission. The PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI. The DFI flag field of the second DCI indicates '0' or does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1's.

[0161] In an embodiment of the present application, optionally, the semi-static transmission is an SPS PDSCH transmission, a second type of configured grant PUSCH transmission, or a semi-static CSI transmission.

[0162] It should be noted that for the method for verifying the PDCCH provided in the embodiments of the present application, the execution subject may be a PDCCH verification device, or a control module in the PDCCH verification device for executing the method for verifying the PDCCH. In the embodiments of the present application, taking the PDCCH verification device executing the method for verifying the PDCCH as an example, the PDCCH verification device provided in the embodiments of the present application is described.

[0163] Please refer to Figure 4 , the embodiments of the present application further provide a PDCCH verification device 40, including:

[0164] A first receiving module 41, configured to receive a first DCI;

[0165] A first verification module 42, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if the target bit position of the first indication field of the first DCI indicates '0', not all '1's, or a preset value. The first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of an NDI field and an RVI field.

[0166] Optionally, the first verification module 42 is configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if the PDCCH transmitting the first DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or does not exist, and the target bit position of the first indication field of the first DCI indicates '0', not all '1's, or a preset value.

[0167] Optionally, the target bit position is one of the following:

[0168] All bit positions;

[0169] Bit positions corresponding to valid PUSCHs;

[0170] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0171] Optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

[0172] Optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

[0173] Optionally, the target bit position indicating non-all '1's means that one position in the target bit position is '0' and the rest are '1's.

[0174] Optionally, if all bit positions of the first indication field indicate '0' or non-all '1's or a preset value, or if the bit positions corresponding to the valid PUSCH of the first indication field all indicate '0', the PDCCH verification device further includes:

[0175] A first determination module, configured to determine that the start and length indication value SLIV used for the activated semi-static transmission is a predefined SLIV among the valid SLIVs in the time domain resource allocation TDRA field of the first DCI.

[0176] Optionally, if the first N bit positions or the last N bit positions of the first indication field indicate '0', the PDCCH verification device further includes:

[0177] A second determination module, configured to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.

[0178] Optionally, if the bit positions corresponding to the valid PUSCH of the first indication field indicate non-all '1's, the PDCCH verification device further includes:

[0179] A third determination module, configured to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, where the target valid PUSCH is the valid PUSCH corresponding to the bit position indicating '0' among the valid PUSCHs corresponding to the first indication field.

[0180] Optionally, the verification device for the PDCCH further includes:

[0181] A second verification module, configured to determine that the first DCI is deactivated for semi-static transmission if the first DCI further meets at least one of the following conditions:

[0182] The HARQ process number field of the first DCI indicates all '0's;

[0183] The modulation and coding scheme MCS field of the first DCI indicates all '0's;

[0184] The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

[0185] Optionally, the verification device for the PDCCH further includes:

[0186] A second receiving module, configured to receive a second DCI;

[0187] A third verification module, configured to determine that the second DCI is used for scheduling retransmission of semi-static transmission if the PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1's.

[0188] Optionally, the semi-static transmission is an SPS PDSCH transmission, a second type of configured grant PUSCH transmission, or a semi-static CSI transmission.

[0189] In the embodiments of the present application, a verification and configuration method for the DCI of the scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is clarified, so that the terminal can accurately determine the timing of activation or deactivation of semi-static transmission.

[0190] The PDCCH verification device in the embodiments of the present application can be a device, or a component, an integrated circuit, or a chip in a terminal. The 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 the terminal 11 listed above, and the non-mobile terminal can be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which are not specifically limited in the embodiments of the present application.

[0191] The PDCCH verification device in the embodiments of the present application can be a device with an operating system. The operating system can be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.

[0192] The PDCCH verification device provided in the embodiments of the present application can implement Figure 2 each process implemented by the method embodiments described above and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0193] It should be noted that for the PDCCH sending method provided in the embodiments of the present application, the execution subject can be the PDCCH sending device, or a control module in the PDCCH sending device for executing the PDCCH sending method. In the embodiments of the present application, the PDCCH sending device is taken as an example to execute the PDCCH sending method to illustrate the PDCCH sending device provided in the embodiments of the present application.

[0194] Please refer to Figure 5 , the embodiments of the present application further provide a PDCCH sending device 50, including:

[0195] A first sending module 51, configured to transmit a first DCI used for activation or deactivation of semi-static transmission, where a target bit position of a first indication field of the first DCI indicates '0' or non-all '1' or a preset value, and the first indication field includes at least one of an NDI field and an RVI field.

[0196] Optionally, the first DCI further satisfies the following conditions: the PDCCH transmitting the first DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, and a DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.

[0197] Optionally, the target bit position is one of the following:

[0198] All bit positions;

[0199] Bit positions corresponding to the valid PUSCH

[0200] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0201] Optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.

[0202] Optionally, the bit positions corresponding to the valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI and a is the size of each PUSCH NDI in the NDI field.

[0203] Optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.

[0204] Optionally, the bit positions corresponding to the valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI and b is the size of each PUSCH RVI in the RVI field.

[0205] Optionally, the first N bit positions or the last N bit positions are the first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0206] Optionally, the target bit position indicating not all '1's means that one position in the target bit positions is '0' and the rest are '1'.

[0207] Optionally, if the first DCI is used for deactivation of semi-static transmission, the first DCI further satisfies at least one of the following conditions:

[0208] The HARQ process number field of the first DCI indicates all '0's;

[0209] The modulation and coding scheme MCS field of the first DCI indicates all '0's;

[0210] The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

[0211] Optionally, the transmission device of the PDCCH further includes:

[0212] A second transmission module, configured to transmit a second DCI for scheduling retransmission used for semi-static transmission, where the PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the valid PUSCH positions in the NDI field of the second DCI indicate all '1's.

[0213] Optionally, the semi-static transmission is SPS PDSCH transmission, or second-type configured grant PUSCH transmission, or semi-static CSI transmission.

[0214] In the embodiments of the present application, a verification and configuration method for a DCI for scheduling Multi-PUSCH for activation or deactivation of semi-static transmission is clarified, so that a terminal can accurately determine the timing of activation or deactivation of semi-static transmission.

[0215] The PDCCH transmission device provided in the embodiments of the present application can implement Figure 3 each process implemented by the method embodiments, and achieve the same technical effects. To avoid repetition, details are not described here again.

[0216] As Figure 6 shown, the embodiments of the present application further provide a communication device 60, including a processor 61, a memory 62, and a program or instruction stored on the memory 62 and executable on the processor 61. For example, when the communication device 60 is a terminal, when the program or instruction is executed by the processor 61, each process of the above-mentioned PDCCH verification method embodiment is implemented, and the same technical effects can be achieved. When the communication device 60 is a network-side device, when the program or instruction is executed by the processor 61, each process of the above-mentioned PDCCH transmission method embodiment is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again.

[0217] Figure 7 It is a schematic diagram of the hardware structure of a terminal for implementing the embodiments of the present application. The terminal 70 includes, but is not limited to: a radio frequency unit 71, a network module 72, an audio output unit 73, an input unit 74, a sensor 75, a display unit 76, a user input unit 77, an interface unit 78, a memory 79, and a processor 710, etc.

[0218] Those skilled in the art can understand that the terminal 70 may further include a power source (such as a battery) for supplying power to each component. The power source may be logically connected to the processor 710 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 7The terminal structure shown 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 have different component arrangements, which will not be elaborated here.

[0219] It should be understood that in the embodiments of the present application, the input unit 74 may include a Graphics Processing Unit (GPU) 741 and a microphone 742. The graphics processor 741 processes the image data of the static pictures or videos obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 76 may include a display panel 761, and the display panel 761 may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 77 includes a touch panel 771 and other input devices 772. The touch panel 771 is also called a touch screen. The touch panel 771 may include two parts: a touch detection device and a touch controller. The other input devices 772 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, which will not be elaborated here.

[0220] In the embodiments of the present application, after receiving the downlink data from the network-side device, the radio frequency unit 71 sends it to the processor 710 for processing; in addition, it sends the uplink data to the network-side device. Generally, the radio frequency unit 71 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0221] The memory 79 can be used to store software programs or instructions and various data. The memory 79 mainly includes a storage program or instruction area and a storage data area. Among them, the storage program or instruction area can store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 79 may include a high-speed random access memory, and may also include a non-volatile memory. Among them, the non-volatile memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (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.

[0222] The processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor. Among them, the application processor mainly processes the operating system, user interface, application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor 710 either.

[0223] Among them, the radio frequency unit 71 is used to receive the first DCI;

[0224] The processor 710 is configured to, if the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission. The first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of the NDI field and the RVI field.

[0225] In the embodiments of the present application, a verification and configuration method for DCI scheduling Multi-PUSCH for activation or deactivation of semi-static transmission is clarified, so that the terminal can accurately determine the timing for activation or deactivation of semi-static transmission.

[0226] Optionally, the processor 710 is further configured to, if the PDCCH transmitting the first DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the target bit position of the first indication field of the first DCI indicates '0' or not all '1' or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission.

[0227] Optionally, the target bit position is one of the following:

[0228] All bit positions;

[0229] Indicating the position of the valid physical uplink shared channel PUSCH;

[0230] The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

[0231] Optionally, the bit positions corresponding to the valid PUSCHs in the NDI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI field.

[0232] Optionally, the bit positions corresponding to the valid PUSCHs in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

[0233] Optionally, the bit positions corresponding to the valid PUSCHs in the RVI field of the first DCI are determined by the number of valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI field.

[0234] Optionally, the bit positions corresponding to the valid PUSCHs in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

[0235] Optionally, the target bit position indicating not all '1's means that one position in the target bit position is '0' and the rest are '1's.

[0236] Optionally, if all bit positions of the first indication field indicate '0' or not all '1's or a preset value, or if the bit positions corresponding to the valid PUSCHs in the first indication field all indicate '0', the processor 710 is further configured to determine that the starting and length indication value SLIV used for the activated semi-static transmission is the predefined SLIV among the valid SLIVs in the time domain resource allocation TDRA field of the first DCI.

[0237] Optionally, if the first N bit positions or the last N bit positions of the first indication field indicate '0', the processor 710 is further configured to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.

[0238] Optionally, if the bit positions corresponding to the valid PUSCHs in the first indication field indicate not all '1's, the processor 710 is further configured to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, where the target valid PUSCH is the valid PUSCH corresponding to the position indicating '0' among the bit positions corresponding to the valid PUSCHs in the first indication field.

[0239] Optionally, the processor 710 is further configured to determine that the first DCI is used for deactivating the semi-static transmission if the first DCI further satisfies at least one of the following conditions:

[0240] The HARQ process number field of the first DCI indicates all '0's;

[0241] The modulation and coding scheme (MCS) field of the first DCI indicates all '0's;

[0242] The frequency domain resource allocation (FDRA) field of the first DCI indicates an invalid resource allocation.

[0243] Optionally, the radio frequency unit 71 is further configured to receive a second DCI;

[0244] The processor 710 is further configured to determine that the second DCI is used for semi-static transmission scheduling retransmission if the PDCCH for transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the valid PUSCH position indication in the NDI field of the second DCI indicates all '1's.

[0245] Optionally, the semi-static transmission is an SPS PDSCH transmission, a second type of configured grant PUSCH transmission, or a semi-static CSI transmission.

[0246] Specifically, an embodiment of the present application further provides a network-side device. As Figure 8 shown, the network device 80 includes: an antenna 81, a radio frequency device 82, and a baseband device 83. The antenna 81 is connected to the radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be sent and sends it to the radio frequency device 82. The radio frequency device 82 processes the received information and then sends it out through the antenna 81.

[0247] The above frequency band processing device may be located in the baseband device 83. The method executed by the network-side device in the above embodiments may be implemented in the baseband device 83. The baseband device 83 includes a processor 84 and a memory 85.

[0248] The baseband device 83 may include, for example, at least one baseband board, and a plurality of chips are arranged on the baseband board. As Figure 8 shown, one of the chips is, for example, a processor 84, which is connected to the memory 85 to call a program in the memory 85 to execute the network device operations shown in the above method embodiments.

[0249] The baseband device 83 may further include a network interface 86 for interacting with the radio frequency device 82. The interface is, for example, a common public radio interface (CPRI).

[0250] Specifically, the network-side device according to the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84. The processor 84 calls the instructions or programs in the memory 85 to execute Figure 3 the methods executed by the modules shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0251] The embodiment of the present application further provides a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the various processes of the above-described embodiment of the PDCCH verification method are implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0252] The embodiment of the present application further provides a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, the various processes of the above-described embodiment of the PDCCH sending method are implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0253] Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0254] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run the network-side device program or instructions to implement the various processes of the above-described embodiment of the PDCCH verification method, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0255] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run the network-side device program or instructions to implement the various processes of the above-described embodiment of the PDCCH sending method, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0256] It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-on-chip, a system chip, a chip system, or a system-on-chip.

[0257] Another embodiment of the present application provides a program product. The program product is stored in a non-volatile storage medium and is executed by at least one processor to implement each process of the above-mentioned embodiment of the PDCCH verification method, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0258] Another embodiment of the present application provides a program product. The program product is stored in a non-volatile storage medium and is executed by at least one processor to implement each process of the above-mentioned embodiment of the PDCCH sending method, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0259] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments 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 the reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0260] Through the description of the above embodiments, 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. Of course, they can also be implemented 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, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to enable a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0261] The embodiments of the present application have been described above with reference to the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them belong to the protection scope of the present application.

Claims

1. A verification method for a Physical Downlink Control Channel (PDCCH), applied to a terminal, characterized in that including: receiving first downlink control information DCI; if the target bit position in the first indication field of the first DCI indicates '0' or not all '1's or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission, the first indication field corresponding to multiple physical uplink shared channels PUSCH, and the first indication field including at least one of a new data indication NDI field and a redundancy version indication RVI field; wherein, if the target bit position in the first indication field of the first DCI indicates '0' or not all '1's or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission includes: if the PDCCH transmitting the first DCI is scrambled by a configured scheduling radio network temporary identifier CS-RNTI or a semi-static scheduling channel state information radio network temporary identifier SP-CSI-RNTI, the deep flow detection DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the target bit position in the first indication field of the first DCI indicates '0' or not all '1's or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission.

2. The method according to claim 1, wherein The target bit position is one of the following: all bit positions; bit positions corresponding to valid PUSCH; the first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

3. The method according to claim 2, wherein The bit positions corresponding to valid PUSCH in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCH scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

4. The method according to claim 2, characterized in that, The bit positions corresponding to valid PUSCH in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCH scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

5. The method according to claim 1, wherein The target bit position indicating not all '1's includes that one position in the target bit positions is '0' and the rest are '1's.

6. The method according to claim 2, characterized in that, If all bit positions in the first indication field indicate '0' or not all '1's or a preset value, or if all bit positions corresponding to valid PUSCH in the first indication field indicate '0', after determining that the first DCI is used for activation or deactivation of semi-static transmission, it further includes: determining that the start and length indication value SLIV used for the activated semi-static transmission is a predefined SLIV among the valid SLIVs in the time domain resource allocation TDRA field of the first DCI.

7. The method according to claim 3, wherein If the first N bit positions or the last N bit positions in the first indication field indicate '0', after determining that the first DCI is used for activation or deactivation of semi-static transmission, it further includes: determining that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA field of the first DCI.

8. The method according to claim 3, wherein If the bit position corresponding to the valid PUSCH in the first indication field indicates not all '1's, after determining that the first DCI is used for activation or deactivation of semi-static transmission, it further includes: Determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA field of the first DCI, where the target valid PUSCH is the valid PUSCH corresponding to the position indicating '0' among the bit positions corresponding to the valid PUSCH in the first indication field.

9. The method according to claim 1, wherein After determining that the first DCI is used for activation or deactivation of semi-static transmission, it further includes: If the first DCI further satisfies at least one of the following conditions, determine that the first DCI is used for deactivation of semi-static transmission: The HARQ process number field of the first DCI indicates all '0's; The modulation and coding scheme (MCS) field of the first DCI indicates all '0's; The frequency domain resource allocation (FDRA) field of the first DCI indicates an invalid resource allocation.

10. The method according to claim 1, wherein It further includes: Receive a second DCI; If the PDCCH transmitting the second DCI is scrambled by a CS-RNTI or an SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the valid PUSCH position in the NDI field of the second DCI indicates all '1's, determine that the second DCI is used for scheduling retransmission of semi-static transmission.

11. The method according to claim 1 or 10, characterized in that, The semi-static transmission is semi-static scheduled physical downlink shared channel (SPS PDSCH) transmission, or second type of configured grant PUSCH transmission, or semi-static CSI transmission.

12. A verification device for a PDCCH, characterized in that, It includes: A first receiving module, configured to receive a first DCI; A first verification module, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if the target bit position in the first indication field of the first DCI indicates '0', not all '1's, or a preset value, where the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of an NDI field and an RVI field; Wherein, if the target bit position in the first indication field of the first DCI indicates '0', not all '1's, or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission includes: If the PDCCH transmitting the first DCI is scrambled by a configured scheduling radio network temporary identifier (CS-RNTI) or a semi-static scheduling channel state information radio network temporary identifier (SP-CSI-RNTI), the deep flow inspection (DFI) flag field of the first DCI indicates '0' or the DFI flag field does not exist, and the target bit position in the first indication field of the first DCI indicates '0', not all '1's, or a preset value, determine that the first DCI is used for activation or deactivation of semi-static transmission.

13. A method for transmitting PDCCH, applied to a network-side device, characterized in that, It includes: Transmit a first DCI for activation or deactivation of semi-static transmission, where the target bit position of the first indication field of the first DCI indicates '0' or not all '1's or a preset value, the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of the NDI field and the RVI field; wherein, the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.

14. The method for transmitting PDCCH according to claim 13, wherein, The target bit position is one of the following: All bit positions; The bit positions corresponding to valid PUSCHs; The first N bit positions or the last N bit positions, where N is a positive integer greater than or equal to 1.

15. The method according to claim 14, wherein The bit positions corresponding to valid PUSCHs in the NDI field of the first DCI are the highest or lowest M'*a bits in the NDI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI field.

16. The method according to claim 14, wherein The bit positions corresponding to valid PUSCHs in the RVI field of the first DCI are the highest or lowest M'*b bits in the RVI field, where M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI field.

17. The method according to claim 13, wherein The target bit position indicating not all '1's includes that one position in the target bit positions is '0' and the rest are '1's.

18. The method according to claim 13, wherein If the first DCI is used for deactivation of semi-static transmission, the first DCI further satisfies at least one of the following conditions: The HARQ process number field of the first DCI indicates all '0's; The modulation and coding scheme MCS field of the first DCI indicates all '0's; The frequency domain resource allocation FDRA field of the first DCI indicates an invalid resource allocation.

19. The method according to claim 13, wherein Further includes: Transmit a second DCI for scheduling retransmission of semi-static transmission, the PDCCH transmitting the second DCI is scrambled by CS-RNTI or SP-CSI-RNTI, the DFI flag field of the second DCI indicates '0' or the DFI flag field does not exist, and the positions of valid PUSCHs in the NDI field of the second DCI indicate all '1's.

20. The method according to claim 13 or 19, characterized in that, The semi-static transmission is SPS PDSCH transmission or the second type of configured grant PUSCH transmission or semi-static CSI transmission.

21. A transmission device for PDCCH, characterized in that, Includes: A first transmission module, configured to transmit a first DCI for activation or deactivation of semi-static transmission, where the target bit position of the first indication field of the first DCI indicates '0' or not all '1's or a preset value, the first indication field corresponds to multiple PUSCHs, and the first indication field includes at least one of the NDI field and the RVI field; Wherein, the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI indicates '0' or the DFI flag field does not exist.

22. A terminal, characterized in that, It includes a processor, a memory, and programs or instructions stored on the memory and executable on the processor. When the programs or instructions are executed by the processor, the steps of the PDCCH verification method according to any one of claims 1 to 11 are implemented.

23. A network-side device, characterized in that, It includes a processor, a memory, and programs or instructions stored on the memory and executable on the processor. When the programs or instructions are executed by the processor, the steps of the PDCCH sending method according to any one of claims 13 to 20 are implemented.

24. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the PDCCH verification method according to any one of claims 1 to 11 are implemented, or the steps of the PDCCH sending method according to any one of claims 13 to 20 are implemented.

Images