CN113965999A

CN113965999A - PDCCH (physical Downlink control channel) checking method, sending method, terminal and network side equipment

Info

Publication number: CN113965999A
Application number: CN202010708044.5A
Authority: CN
Inventors: 李�根; 李娜
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2020-07-21
Filing date: 2020-07-21
Publication date: 2022-01-21
Also published as: WO2022017354A1

Abstract

The application discloses a PDCCH (physical Downlink control channel) checking method, a PDCCH sending method, a terminal and network side equipment, and belongs to the technical field of wireless communication. The method for verifying the PDCCH applied to the terminal comprises the following steps: receiving a first DCI; if the target bit position of the first indication field of the first DCI indicates '0' or non-full '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission, 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. The application specifies a method for validating and configuring DCI for scheduling Multi-PUSCH for activating or deactivating semi-static transmission, so that a terminal can accurately determine the activation or deactivation opportunity of semi-static transmission.

Description

PDCCH (physical Downlink control channel) checking method, sending method, terminal and network side equipment

Technical Field

The application belongs to the technical field of wireless communication, and particularly relates to a PDCCH checking method, a PDCCH sending method, a terminal and network side equipment.

Background

In New Radio Unlicensed spectrum (NRU), scheduling of multiple Physical Uplink Shared channels (Multi-PUSCH) is introduced into DCI format0_1 in Rel-16, but when activation or deactivation of semi-static transmission in the related art is designed by using Downlink Control Information (DCI), only activation or deactivation of semi-static transmission by using DCI scheduling a Single PUSCH (Single-PUSCH) is considered, and how to perform activation or deactivation of semi-static transmission by using DCI scheduling Multi-PUSCH is a problem to be solved.

Disclosure of Invention

An object of the embodiments of the present application is to provide a PDCCH checking method, a PDCCH sending method, a terminal, and a network side device, so as to solve a problem how to use DCI scheduling Multi-PUSCH to perform activation or deactivation of semi-static transmission.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, a PDCCH checking method is provided, and is applied to a terminal, and the method includes:

receiving first Downlink Control Information (DCI);

if the target bit position of the first indication field of the first DCI indicates '0' or non-full '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission, where the first indication field corresponds to a plurality of Physical Uplink Shared Channels (PUSCHs), and the first indication field includes at least one of an NDI field and an RVI field.

In a second aspect, an apparatus for checking a PDCCH is provided, including:

a first receiving module, configured to receive a first DCI;

a first checking module, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' or a preset value, where the first indication field corresponds to a plurality of Physical Uplink Shared Channels (PUSCHs), and the first indication field includes at least one of an NDI field and an RVI field.

Optionally, the first checking module 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 CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates that '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 non-full '1' or a preset value.

Optionally, the target bit position is one of the following:

all bit positions;

bit positions corresponding to the valid PUSCH;

the first N bit positions or the last N bit positions, N being a positive integer greater than or equal to 1.

Optionally, bit positions corresponding to the effective PUSCHs in the NDI domain of the first DCI are the highest or lowest M '× a bits in the NDI domain, M' is the number of the effective PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI domain.

Optionally, bit positions corresponding to valid PUSCHs in the RVI domain of the first DCI are the highest or lowest M '× b bits in the RVI domain, M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI domain.

Optionally, the target bit position indication not all '1' includes that one of the target bit positions is '0' and the rest are '1'.

Optionally, if all bit positions of the first indication field indicate '0' or non-full '1' or a preset value, or bit positions corresponding to an effective PUSCH of the first indication field all indicate '0', the apparatus for verifying a PDCCH further includes:

a first determining module to determine a starting and length indication value, SLIV, used for the activated semi-static transmission to be a predefined SLIV of valid SLIVs in a time domain resource allocation, TDRA, domain of the first DCI.

Optionally, if the first N bit positions or the last N bit positions of the first indication field indicate '0', the apparatus for verifying the PDCCH further includes:

a second determining module, configured to determine that the SLIV used for the activated semi-static transmission is a SLIV corresponding to a PUSCH in the first N bit positions or the last N bit positions in a TDRA domain of the first DCI.

Optionally, if the bit position corresponding to the valid PUSCH in the first indication field indicates not all '1', the apparatus for verifying the PDCCH further includes:

a third determining module, configured to determine that the SLIV used for the activated semi-static transmission is the SLIV corresponding to a target valid PUSCH in the TDRA domain of the first DCI, where the target valid PUSCH is a valid PUSCH corresponding to a position indicating '0' in a bit position corresponding to a valid PUSCH in the first indication domain.

Optionally, the apparatus for verifying the PDCCH further includes:

a second checking module, configured 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:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

and the FDRA domain of the frequency domain resource allocation of the first DCI indicates invalid resource allocation.

Optionally, the apparatus for verifying the PDCCH further includes:

a second receiving module, configured to receive a second DCI;

and the third checking module is used for determining that the second DCI is used as scheduling retransmission of semi-static transmission if the PDCCH for 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 effective PUSCH position in the NDI field of the second DCI indicates all '1'.

Optionally, the semi-persistent transmission is SPS PDSCH transmission or second type of configuration grant PUSCH transmission or semi-persistent CSI transmission.

In a third aspect, a PDCCH sending method is provided, and is applied to a network side device, and includes:

transmitting a first DCI used for activation or deactivation of semi-static transmission, wherein 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.

In a fourth aspect, an apparatus for transmitting a PDCCH is provided, including:

a first transmitting module, configured to transmit a first DCI for activation or deactivation of semi-static transmission, wherein a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' or a preset value, and the first indication field includes at least one of an NDI field and an RVI field.

Optionally, the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI is indicated as '0' or does not exist.

Optionally, the target bit position is one of the following:

all bit positions;

bit positions corresponding to the valid PUSCH;

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:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

Optionally, the apparatus for transmitting PDCCH further includes:

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

In a fifth aspect, there is provided a terminal comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to the first aspect.

In a sixth aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and when executed by the processor, the program or instructions implement the steps of the method according to the third aspect.

In a seventh aspect, there is provided a readable storage medium on which a program or instructions are stored, which program or instructions, when executed by a processor, implement the steps of the method according to the first aspect, or implement the steps of the method according to the third aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction, implement the method according to the first aspect, or implement the method according to the third aspect.

In a ninth aspect, there is provided a program product stored on a non-volatile storage medium, the program product being executable by at least one processor to implement a method as in the first aspect, or to implement a method as in the third aspect.

In the embodiment of the application, a method for verifying and configuring the DCI of scheduling Multi-PUSCH used for activation or deactivation of semi-static transmission is made clear, so that a terminal can accurately determine the activation or deactivation opportunity of semi-static transmission.

Drawings

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

fig. 2 is a flowchart illustrating a PDCCH verification method according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a method for transmitting a PDCCH according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a PDCCH verification apparatus according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a PDCCH transmission apparatus according to an embodiment of the present application;

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

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

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

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may 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 techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for purposes of example, and NR terminology is used in much of the description below, although the techniques may also be applied to applications other than NR system applications, such as 6 th generation (6 th generation)^thGeneration, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may 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 node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and 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 a specific type of the Base Station is not limited.

For a scenario where DCI schedules a Single PUSCH (Single-PUSCH), whether DCI is used to activate or deactivate semi-static transmission is checked according to table 1 and table 2.

Table 1 configuration of DCI activating semi-static transmission

Table 2 configuration for deactivating semi-static transmissions

In the related art, when the activation or deactivation of the semi-static transmission is designed by using the DCI, only the activation or deactivation of the semi-static transmission by using the DCI scheduling a single PUSCH is considered, and how to use the DCI scheduling Multi-PUSCH to activate or deactivate the semi-static transmission is a problem to be solved.

The PDCCH verification method, the PDCCH transmission method, the terminal and the network side device provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

Referring to fig. 2, an embodiment of the present application provides a method for checking a Physical Downlink Control Channel (PDCCH), which is applied to a terminal, and includes:

step 21: receiving a first DCI;

the first DCI is DCI format0_1 supporting scheduling of Multi-PUSCH.

Step 22: determining that the first DCI is used for activation or deactivation of semi-static transmission if a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' or a preset value, where the first indication field corresponds to a plurality of PUSCHs, and the first indication field includes at least one of a New Data Indicator (NDI) field and a Redundancy Version Indicator (RVI) field.

In this embodiment of the application, the NDI field is an NDI of an enabled Transport Block (TB) in DCI, and is used to indicate a time domain position of scheduled PUSCH transmission.

In the embodiment of the present application, not all '1's means that all of the target bit positions indicate '1', for example, one of the target bit positions is '0', and the rest are '1'.

In the embodiment of the present application, the preset value refers to a value different from all '0' and not all '1', for example, '10', and the like. The preset value may be agreed upon by a protocol.

In this embodiment, optionally, if the target bit position of the first indication field of the first DCI indicates '0' or non-full '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission includes:

and if the PDCCH for 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), indicating that a Deep Flow Detection (DFI) flag field of the first DCI is '0' or a DFI flag field does not exist, indicating that a target bit position of a first indication field of the first DCI is '0' or not all '1' or a preset value, and determining that the first DCI is used for activation or deactivation of semi-persistent transmission.

In the embodiment of the present application, when it is detected that a PDCCH is scrambled by a CS-RNTI or an SP-CSI-RNTI, it may be considered that a first DCI in the PDCCH is used as a retransmission of a Semi-Persistent Scheduling (SPs) Physical Downlink Shared Channel (PDSCH) or a configuration grant (Configured grant) PUSCH, or used as an activation or Semi-Persistent CSI transmission of an SPs PDSCH or a second Type of configuration grant (Type 2Configured grant) PUSCH, or used as a deactivation of the SPs PDSCH or the Type 2Configured grant PUSCH or the Semi-Persistent CSI transmission, or used as a transmission of a DFI.

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

Optionally, the semi-persistent transmission is SPS PDSCH transmission or Type 2Configured grant PUSCH transmission or semi-persistent CSI transmission.

In the embodiment of the application, a method for verifying and configuring the DCI used for activating or deactivating the semi-static transmission and scheduling the Multi-PUSCH is made clear, so that the terminal can accurately determine the activation or deactivation time of the semi-static transmission.

The target bit position of the first indication field of the first DCI in the above embodiment is described below by way of example.

In some embodiments of the present application, optionally, the target bit positions of the first indication field are all 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 indicates '0' or the DFI flag field does not exist, and all 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 position indications '0' may also be described as indicating all '0's.

In this embodiment of the application, if all bit positions of the first indication field indicate '0' or non-full '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission further includes: determining a Start and Length Indicator Value (SLIV) used for the activated semi-static transmission to be a predefined SLIV of valid SLIVs in a Time Domain Resource Allocation (TDRA) domain of the first DCI.

In this embodiment of the application, if a Multi-PUSCH TDRA table is configured, the terminal may determine the size of each field in the first DCI according to the Multi-PUSCH TDRA table, and assuming that the maximum number of PUSCHs that can be scheduled by the Multi-PUSCH TDRA table is M, the size of the NDI field in the first DCI is M a bits, a is the size of each PUSCH NDI in the NDI field, a is M b bits, and b is the size of each PUSCH RVI in the first DCI.

The terminal may determine the Multi-PUSCH TDRA table according to table 3.

TABLE 3

As can be seen from table 3:

1) if the PUSCH time domain resource allocation table (PUSCH-time domain allocation list) is not configured in the PUSCH-ConfigCommon, the PUSCH time domain resource allocation table (PUSCH-time domain allocation list) is not configured in the PUSCH-Config, the PUSCH time domain resource allocation table (PUSCH-time domain allocation list-time domain _1) is not configured in the PUSCH-Config, the DCI format0_1 is not configured in the PUSCH-Config, and the PUSCH time domain resource allocation table (PUSCH-time domain allocation list-multimedia PUSCH) is not configured in the PUSCH-Config, the Default a table is determined to be the Multi-PUSCH TDRA table.

2) If a PUSCH time domain resource allocation table (PUSCH-time domain allocation list) is configured in the PUSCH-ConfigCommon, a PUSCH time domain resource allocation table (PUSCH-time domain allocation list) is not configured in the PUSCH-Config, a PUSCH time domain resource allocation table (PUSCH-time domain allocation list-time dciformation list) is not configured in the PUSCH-Config, a DCI format0_1 is not configured in the PUSCH-Config, and a PUSCH time domain resource allocation table (PUSCH-time domain allocation list-multimedia PUSCH) is not configured in the PUSCH-Config, the PUSCH time domain resource allocation table (PUSCH-time domain allocation list-multimedia) configured in the PUSCH-ConfigCommon is determined as the Multi-tdpusch table.

3) If the PUSCH time domain resource allocation table (PUSCH-time domain allocation table) is configured or not configured in the PUSCH-ConfigCommon, the PUSCH time domain resource allocation table (PUSCH-time domain allocation table) is configured in the PUSCH-Config, the PUSCH time domain resource allocation table (PUSCH-time domain allocation table) is not configured in the DCI format0_1 in the PUSCH-Config, the PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format 0_1) is not configured in the PUSCH-Config, and the PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format PUSCH) is not configured in the PUSCH-Config, the PUSCH time domain resource allocation table (PUSCH-time domain allocation table) configured in the PUSCH-Config is determined to be used as the Multi-tdpusch table.

4) If a PUSCH time domain resource allocation table (PUSCH-time domain allocation table) is configured or not configured in the PUSCH-ConfigCommon, a PUSCH time domain resource allocation table (PUSCH-time domain allocation table) is configured or not configured in the PUSCH-Config, a PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format dciformation 0_1) is configured in the PUSCH-Config with DCI format0_1, and a PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format PUSCH) is not present in the PUSCH-Config, a PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format 0_1) of the DCI format0_1 configured in the PUSCH-Config is determined as the PUSCH time domain resource allocation table (PUSCH-time domain allocation table-format 0_ 1).

5) If a PUSCH time domain resource allocation table (PUSCH-timesdomainnalocationlist) is configured or not configured in the PUSCH-ConfigCommon, a PUSCH time domain resource allocation table (PUSCH-timesdomainnalocationlist) is configured or not configured in the PUSCH-Config, a PUSCH time domain resource allocation table (PUSCH-timesdomainnalocationlist-DCI 0_1) where DCI format0_1 does not exist in the PUSCH-Config, and a Multi PUSCH time domain resource allocation table (PUSCH-timesdomainnalocationlist-multimedia PUSCH) is configured in the PUSCH-Config, the Multi PUSCH time domain resource allocation table (PUSCH-timesdomainnalocationlist-multimedia) configured in the PUSCH-Config is determined as the Multi PUSCH-PUSCH table.

Assume actual tones in the TDRA domain in the first DCIThe number of valid PUSCHs of degree is M' (1 ═<M’<M)), each PUSCH corresponds to one SLIV, for example, the SLIVs corresponding to the M' PUSCHs may be respectively SLIVs₀,SLIV₁,…,SLIV_M’-1. The effective SLIV refers to the SLIV corresponding to the actually scheduled effective PUSCH, e.g. SLIV₀。

In some embodiments of the present application, optionally, the target bit position of the first indication field is a bit position corresponding to a 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, it is determined that the first DCI is used for activation or deactivation of semi-static transmission. The bit position indication '0' corresponding to the valid PUSCH can also be described as all '0' of the position indications of the valid PUSCH.

In this embodiment of the application, optionally, the bit position corresponding to the effective PUSCH in the NDI domain of the first DCI is determined by the number of the effective PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI domain.

In this embodiment of the application, optionally, bit positions corresponding to the effective PUSCHs in the NDI domain of the first DCI are the highest or lowest M '× a bits in the NDI domain, M' is the number of the effective PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI domain. That is, the bit position corresponding to the valid PUSCH of the NDI field of the first DCI indicates ' 0 ' or not all ' 1 ' or a preset value, which means that the highest or lowest M ' × a bits in the NDI field indicate ' 0 ' or not all ' 1 ' or a preset value.

In this embodiment of the application, optionally, the bit position corresponding to the effective PUSCH in the RVI domain of the first DCI is determined by the number of the effective PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI domain.

In this embodiment of the application, optionally, bit positions corresponding to the valid PUSCHs in the RVI domain of the first DCI are the highest or lowest M '× b bits in the RVI domain, M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI domain. That is, the bit position corresponding to the valid PUSCH of the RVI field of the first DCI indicates ' 0 ' or non-full ' 1 ' or a preset value, which means that the highest or lowest M ' × b bits in the RVI field indicate ' 0 ' or non-full ' 1 ' or a preset value.

In this embodiment of the present application, optionally, if the bit position corresponding to the valid PUSCH in the first indication field indicates '0', after determining that the first DCI is used for activation or deactivation of semi-static transmission, the method further includes: determining a SLIV used by the activated semi-static transmission to be a predefined SLIV of valid SLIVs in a Time Domain Resource Allocation (TDRA) domain of the first DCI.

In this embodiment of the application, optionally, if the bit position corresponding to the valid PUSCH in the first indication field indicates non-all '1', determining that the first DCI is used for activation or deactivation of semi-static transmission further includes: determining the SLIV used for the activated semi-static transmission to be a SLIV corresponding to a target effective PUSCH in a TDRA domain of the first DCI, wherein the target effective PUSCH is an effective PUSCH corresponding to a position indicating '0' in bit positions corresponding to an effective PUSCH in the first indication domain.

In some embodiments of the present application, optionally, the target bit position of the first indication field is 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 indicates '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. A positive integer indication of '0' for the first N bit positions or the last N bit positions 1 may also be described as indicating all '0' for the first N bit positions or the last N bit positions.

In this embodiment 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.

In this embodiment of the application, optionally, if the first N bit positions or the last N bit positions of the first indication field indicate '0', after determining that the first DCI is used for activation or deactivation of semi-static transmission, the method further includes: determining the SLIV used for the activated semi-static transmission as the SLIV corresponding to the PUSCH with the first N bit positions or the last N bit positions in the TDRA domain of the first DCI (e.g., SLIV0 or SLIV_M’-1)。

In this embodiment of the present application, optionally, after determining that the first DCI is used for activation or deactivation of semi-static transmission, the method further includes: determining that the first DCI is to be used for deactivation of semi-static transmission if the first DCI further satisfies at least one of the following conditions:

the HARQ process number field of the first DCI indicates all '0';

a Modulation and Coding Scheme (MCS) field of the first DCI indicates all '0';

a Frequency Domain Resource Allocation (FDRA) field of the first DCI indicates an invalid resource allocation. The FDRA domain is used for indicating frequency domain resources of a scheduled PUSCH.

That is, if the above condition is not satisfied, the first DCI is used as activation of semi-static transmission.

In this embodiment of the application, optionally, the method for verifying the PDCCH further includes:

receiving a second DCI;

and if the PDCCH for 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 effective PUSCH position in the NDI field of the second DCI indicates all '1', and the second DCI is determined to be used as scheduling retransmission of semi-static transmission.

The PDCCH verification method according to the present application will be described below with reference to specific embodiments.

The first embodiment of the invention:

when a Multi-PUSCH TDRA table is configured, DCI format0_1 scrambled by CS-RNTI refers to the Multi-PUSCH TDRA table. Assuming that the configured Multi-PUSCH TDRA table can schedule 4 PUSCHs at maximum, when the TDRA field of the DCI indicates that the scheduling is greater than 1 PUSCH, the NDI field in the DCI is 4 bits, and the RVI field is also 4 bits.

At this time, the UE considers the PDCCH as DCI activating semi-static transmission if one of the following conditions is satisfied:

1. NDI and RVI of DCI is '0000';

2. the number of valid PUSCHs indicated by the TDRA field in the DCI (assumed to be 2), NDI and RVI are '00 xx';

3. the 1 st bit in NDI and RVI of DCI is '0', i.e. NDI and RVI are '0 xxx';

4. the number of valid PUSCHs indicated by the TDRA field in DCI (assumed to be 2) and NDI and RVI are '01 xx' or '10 xx'.

Wherein, for '01 xx', SLIV₀Is used; for '10 xx', SLIV1 is used.

X is 0 or 1, or a predefined value.

Embodiment two of the present invention:

when configuring the Multi-PUSCH TDRA table, the SP-CSI-RNTI scrambled DCI format0_1 refers to the Multi-PUSCH TDRA table. Assuming that the configured Multi-PUSCH TDRA table can schedule 4 PUSCHs at maximum, when the TDRA field of the DCI indicates that scheduling is greater than 1 PUSCH, the NDI field in the DCI is 4 bits, and the RVI field is also 4 bits.

1. the RVI of the DCI is '0000';

2. the number of valid PUSCHs (assumed to be 2) indicated by the TDRA field in the DCI, and the RVI is '00 xx';

3. the 1 st bit in the RVI of the DCI is '0', i.e., the RVI is '0 xxx';

4. the number of valid PUSCHs (assumed to be 2) indicated by the TDRA field in the DCI, and the RVI is '01 xx' or '10 xx'.

Wherein, for '01 xx', SLIV₀Is used; for '10 xx', SLIV1 is used.

X is 0 or 1, or a predefined value.

Referring to fig. 3, an embodiment of the present application further provides a method for sending a PDCCH, which is applied to a network side device, and includes:

step 31: transmitting a first DCI used for activation or deactivation of semi-static transmission, wherein 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.

In this embodiment of the present application, optionally, the first DCI further satisfies the following condition: the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI is indicated as '0' or the DFI flag field is absent.

In this embodiment of the application, optionally, the target bit position is one of the following:

all bit positions;

bit positions corresponding to the valid PUSCH;

In this embodiment of the application, optionally, bit positions corresponding to the effective PUSCHs in the NDI domain of the first DCI are the highest or lowest M '× a bits in the NDI domain, M' is the number of the effective PUSCHs scheduled by the first DCI, and a is the size of each PUSCH NDI in the NDI domain.

In this embodiment of the application, optionally, bit positions corresponding to the valid PUSCHs in the RVI domain of the first DCI are the highest or lowest M '× b bits in the RVI domain, M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI domain.

In this embodiment of the application, optionally, the target bit position indication that all '1's are not included includes that one of the target bit positions is '0' and the rest is '1'.

In this embodiment 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:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

In this embodiment of the application, optionally, the sending method of the PDCCH further includes:

transmitting a second DCI for scheduling retransmission for semi-static transmission, a PDCCH transmitting the second DCI being scrambled by CS-RNTI or SP-CSI-RNTI, a DFI flag field of the second DCI being indicated as '0' or a DFI flag field being absent, and valid PUSCH positions in an NDI field of the second DCI indicating all '1'.

In this embodiment of the application, optionally, the semi-persistent transmission is SPS PDSCH transmission or configuration grant PUSCH transmission of the second type or semi-persistent CSI transmission.

It should be noted that, in the PDCCH checking method provided in the embodiment of the present application, the execution subject may be a checking apparatus of the PDCCH, or a control module in the checking apparatus of the PDCCH, configured to execute the PDCCH checking method. In the embodiment of the present application, a method for performing PDCCH verification by using a PDCCH verification apparatus is taken as an example, and the PDCCH verification apparatus provided in the embodiment of the present application is described.

Referring to fig. 4, an embodiment of the present application further provides an apparatus 40 for checking a PDCCH, including:

a first receiving module 41, configured to receive the first DCI;

a first checking module 42, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' 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.

Optionally, the first checking 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 CS-RNTI or SP-CSI-RNTI, the DFI flag field of the first DCI indicates that '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 non-full '1' or a preset value.

Optionally, the target bit position is one of the following:

all bit positions;

bit positions corresponding to the valid PUSCH;

Optionally, the apparatus for verifying the PDCCH further includes:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

Optionally, the apparatus for verifying the PDCCH further includes:

a second receiving module, configured to receive a second DCI;

The PDCCH checking apparatus in the embodiment of the present application may be an apparatus, or may also be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the above-listed type of terminal 11, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a Television (TV), a teller machine, a kiosk, or the like, and the embodiments of the present application are not limited in particular.

The PDCCH verification apparatus in the embodiment of the present application may be an apparatus having an operating system. The operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, and embodiments of the present application are not limited specifically.

The PDCCH checking apparatus provided in this embodiment of the present application can implement each process implemented in the method embodiment of fig. 2, and achieve the same technical effect, and for avoiding repetition, details are not repeated here.

In the PDCCH transmission method according to the embodiment of the present application, the execution subject may be a PDCCH transmission apparatus, or a control module in the PDCCH transmission apparatus for executing the PDCCH transmission method. In the embodiments of the present application, a PDCCH transmission apparatus that executes a PDCCH transmission method will be described as an example.

Referring to fig. 5, an embodiment of the present application further provides a device 50 for sending a PDCCH, including:

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

Optionally, the first DCI further satisfies the following condition: the PDCCH transmitting the first DCI is scrambled by CS-RNTI or SP-CSI-RNTI, and the DFI flag field of the first DCI is indicated as '0' or the DFI flag field is absent.

Optionally, the target bit position is one of the following:

all bit positions;

bit positions corresponding to the valid PUSCH;

Optionally, the bit position corresponding to the effective PUSCH in the NDI domain of the first DCI is determined by the number of the effective PUSCHs scheduled by the first DCI and the size of each PUSCH NDI in the NDI domain.

Optionally, the bit position corresponding to the valid PUSCH in the RVI domain of the first DCI is determined by the number of the valid PUSCHs scheduled by the first DCI and the size of each PUSCH RVI in the RVI domain.

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

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

Optionally, the apparatus for transmitting PDCCH further includes:

The PDCCH transmitting apparatus according to the embodiment of the present application can implement each process implemented by the method embodiment of fig. 3, and achieve the same technical effect, and for avoiding repetition, details are not described here again.

As shown in fig. 6, an embodiment of the present application further provides a communication device 60, which includes a processor 61, a memory 62, and a program or an instruction stored in the memory 62 and executable on the processor 61, for example, when the communication device 60 is a terminal, the program or the instruction is executed by the processor 61 to implement the processes of the above PDCCH verification method embodiment, and the same technical effect can be achieved. When the communication device 60 is a network-side device, the program or the instruction is executed by the processor 61 to implement the processes of the above-mentioned PDCCH sending method embodiment, and the same technical effect can be achieved, and for avoiding repetition, the details are not described here again.

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

It will be appreciated by those skilled in the art that terminal 70 may also include a power supply (e.g., a battery) for powering the various components, which may be logically coupled to processor 710 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The terminal structure shown in fig. 7 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or combine some components, or have a different arrangement of components, and will not be described again here.

It should be understood that, in the embodiment of the present application, the input Unit 74 may include a Graphics Processing Unit (GPU) 741 and a microphone 742, and the Graphics Processing Unit 741 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing 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, or the like. The user input unit 77 includes a touch panel 771 and other input devices 772. A touch panel 771 also referred to as a touch screen. The touch panel 771 may include two parts of a touch detection device and a touch controller. Other input devices 772 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 71 receives downlink data from a network side device and then processes the downlink data in the processor 710; in addition, the uplink data is sent to the network side equipment. Typically, 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, and the like.

Memory 79 may be used to store software programs or instructions as well as various data. The memory 79 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 79 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable PROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 710 may include one or more processing units; alternatively, processor 710 may integrate an application processor that handles primarily the operating system, user interface, and application programs or instructions, etc. and a modem processor that handles primarily wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into processor 710.

The radio frequency unit 71 is configured to receive the first DCI;

a processor 710, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' 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.

Optionally, the processor 710 is further 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 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 of the first indication field of the first DCI indicates '0' or not all '1' or a preset value.

Optionally, the target bit position is one of the following:

all bit positions;

indicating the position of a valid Physical Uplink Shared Channel (PUSCH);

Optionally, if all bit positions of the first indication field indicate '0' or non-full '1' or a preset value, or bit positions corresponding to an effective PUSCH of the first indication field all indicate '0', the processor 710 is further configured to determine a starting point and a length indication value SLIV used by the activated semi-static transmission to be a predefined SLIV in an effective SLIV in the TDRA field of the time domain resource allocation for the first DCI.

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 activated SLIV used for the 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.

Optionally, if the bit position corresponding to the valid PUSCH in the first indication domain indicates non-full '1', the processor 710 is further configured to determine that the activated SLIV used for the semi-static transmission is the SLIV corresponding to the target valid PUSCH in the TDRA domain of the first DCI, and the target valid PUSCH is the valid PUSCH corresponding to the position indicating '0' in the bit position corresponding to the valid PUSCH in the first indication domain.

Optionally, the processor 710 is further configured 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:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

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

the processor 710 is further configured to determine that the second DCI is used as a scheduling retransmission for semi-static transmission 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 in the NDI field of the second DCI indicates all '1'.

Specifically, the embodiment of the application further provides a network side device. As shown in fig. 8, the network device 80 includes: antenna 81, radio frequency device 82, baseband device 83. The antenna 81 is connected to a radio frequency device 82. In the uplink direction, the rf device 82 receives information via the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes information to be transmitted and transmits the information to the rf device 82, and the rf device 82 processes the received information and transmits the processed information through the antenna 81.

The above band processing means may be located in the baseband device 83, and the method performed by the network side device in the above embodiment may be implemented in the baseband device 83, where the baseband device 83 includes a processor 84 and a memory 85.

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

The baseband device 83 may further include a network interface 86 for exchanging information with the radio frequency device 82, such as a Common Public Radio Interface (CPRI).

Specifically, the network side device of the embodiment of the present invention further includes: the instructions or programs stored in the memory 85 and executable on the processor 84, and the processor 84 calls the instructions or programs in the memory 85 to execute the methods executed by the modules shown in fig. 3, and achieve the same technical effects, which are not described herein for avoiding repetition.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above PDCCH checking method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the above-mentioned PDCCH sending method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

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 Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, where 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 an instruction, to implement each process of the embodiment of the PDCCH checking method, and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

The embodiment of the present application further provides a chip, where 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 an instruction, to implement each process of the sending method embodiment of the PDCCH, and can achieve the same technical effect, and in order to avoid repetition, the details are not repeated here.

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

The embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the above embodiment of the PDCCH verification method, and the same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

The embodiment of the present application further provides a program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement each process of the above embodiment of the sending method for PDCCH, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

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

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for checking a Physical Downlink Control Channel (PDCCH) is applied to a terminal, and is characterized by comprising the following steps:

receiving first Downlink Control Information (DCI);

if the target bit position of the first indication field of the first DCI indicates '0' or non-full '1' or a preset value, determining that the first DCI is used for activation or deactivation of semi-static transmission, where the first indication field corresponds to a plurality of Physical Uplink Shared Channels (PUSCHs), and the first indication field includes at least one of a New Data Indication (NDI) field and a Redundancy Version Indication (RVI) field.

2. The method of claim 1, wherein 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 activation or deactivation of the first DCI for semi-static transmission comprises:

if the PDCCH for transmitting the first DCI is scrambled by a configuration scheduling radio network temporary identifier (CS-RNTI) or a semi-static scheduling channel state information radio network temporary identifier (SP-CSI-RNTI), the depth flow Detection (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 non-full '1' or a preset value, the first DCI is determined to be used for activation or deactivation of semi-static transmission.

3. The method according to claim 1 or 2, wherein the target bit position is one of:

all bit positions;

bit positions corresponding to the valid PUSCH;

4. The method of claim 3, wherein a bit position corresponding to a valid PUSCH in the NDI domain of the first DCI is a highest or lowest M '. a bits in the NDI domain, M' is a number of valid PUSCHs scheduled by the first DCI, and a is a size of each PUSCH NDI in the NDI domain.

5. The method of claim 3, wherein the bit positions corresponding to the valid PUSCHs in the RVI domain of the first DCI are the highest or lowest M '. bB bits in the RVI domain, M' is the number of valid PUSCHs scheduled by the first DCI, and b is the size of each PUSCH RVI in the RVI domain.

6. The method according to claim 1 or 2, wherein the target bit positions indicating not all '1's comprises one of the target bit positions being '0' and the rest being '1'.

7. The method of claim 3, wherein if all bit positions of the first indication field indicate '0' or non-full '1' or a preset value, or bit positions corresponding to a valid PUSCH of the first indication field indicate '0', determining that the first DCI is used for activation or deactivation of semi-static transmission further comprises:

determining a starting and length indication value, SLIV, used for the activated semi-static transmission to be a predefined SLIV of valid SLIVs in a time domain resource allocation, TDRA, domain of the first DCI.

8. The method of claim 3, wherein determining that the first DCI is to be used for activation or deactivation of semi-static transmission further comprises, if the first N bit positions or the last N bit positions of the first indication field indicate '0':

determining the SLIV used for the activated semi-static transmission as the SLIV corresponding to the PUSCH in the first N bit positions or the last N bit positions in the TDRA domain of the first DCI.

9. The method of claim 3, wherein determining that the first DCI is used for activation or deactivation of semi-static transmission further comprises, if the bit position corresponding to the valid PUSCH in the first indication field indicates a non-all '1':

determining the SLIV used for the activated semi-static transmission to be a SLIV corresponding to a target effective PUSCH in a TDRA domain of the first DCI, wherein the target effective PUSCH is an effective PUSCH corresponding to a position indicating '0' in bit positions corresponding to an effective PUSCH in the first indication domain.

10. The method of claim 1 or 2, wherein determining that the first DCI is used for activation or deactivation of semi-static transmission further comprises:

determining that the first DCI is to be used for deactivation of semi-static transmission if the first DCI further satisfies at least one of the following conditions:

the HARQ process number field of the first DCI indicates all '0';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

11. The method of claim 1, further comprising:

receiving a second DCI;

12. The method according to claim 1 or 11, wherein the semi-persistent transmission is a semi-persistent scheduling physical downlink shared channel (SPS) PDSCH transmission or a second type of configuration grant PUSCH transmission or a semi-persistent CSI transmission.

13. An apparatus for checking a PDCCH, comprising:

a first receiving module, configured to receive a first DCI;

a first checking module, configured to determine that the first DCI is used for activation or deactivation of semi-static transmission if a target bit position of a first indication field of the first DCI indicates '0' or non-full '1' 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.

14. A sending method of PDCCH is applied to network side equipment, and is characterized by comprising the following steps:

15. The transmission method of the PDCCH according to claim 14, 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.

16. The method of claim 14 or 15, wherein the target bit position is one of:

all bit positions;

bit positions corresponding to the valid PUSCH;

17. The method of claim 16, wherein a bit position corresponding to a valid PUSCH in the NDI domain of the first DCI is a highest or lowest M '× a bits in the NDI domain, M' is a number of valid PUSCHs scheduled by the first DCI, and a is a size of each PUSCH NDI in the NDI domain.

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

19. The method according to claim 14 or 15, wherein the target bit positions indicating not all '1's comprises one of the target bit positions being '0' and the rest being '1'.

20. The method according to claim 14 or 15, 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';

a modulation and coding scheme, MCS, field of the first DCI indicates all '0';

21. The method of claim 14, further comprising:

22. The method of claim 14 or 21, wherein the semi-persistent transmission is an SPS PDSCH transmission or a second type of configuration grant PUSCH transmission or a semi-persistent CSI transmission.

23. An apparatus for transmitting a PDCCH, comprising:

24. A terminal comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the method of checking the PDCCH according to any one of claims 1 to 12.

25. A network side device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for transmitting the PDCCH according to any one of claims 14 to 22.

26. A readable storage medium, on which a program or instructions are stored, which when executed by a processor, implement the method of checking the PDCCH according to any one of claims 1-12 or the steps of the method of transmitting the PDCCH according to any one of claims 14-22.